Skip to content

Jest globals different from source code globals? #2048

@kentcdodds

Description

@kentcdodds

Do you want to request a feature or report a bug?

bug

What is the current behavior?

In some cases, when source code does stuff with built-in globals like Object, Array, etc. it appears that those built-in globals are not the same as the globals available in the test environment.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal repository on GitHub that we can npm install and npm test.

Still working on figuring out a reliable way to reproduce this in an isolated environment... Stand by...

What is the expected behavior?

The globals should be the same in both environments

Run Jest again with --debug and provide the full configuration it prints. Please mention your node and npm version and operating system.

forthcoming...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions