-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Statement about NODE_ENV wrong #7369
Comments
Wanna send a PR for that? |
How about
|
lukas-zech-software
added a commit
to lukas-zech-software/jest
that referenced
this issue
Nov 19, 2018
lukas-zech-software
added a commit
to lukas-zech-software/jest
that referenced
this issue
Nov 19, 2018
lukas-zech-software
added a commit
to lukas-zech-software/jest
that referenced
this issue
Nov 19, 2018
lukas-zech-software
added a commit
to lukas-zech-software/jest
that referenced
this issue
Nov 22, 2018
rickhanlonii
pushed a commit
that referenced
this issue
Nov 22, 2018
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
🐛 Bug Report
The Using Babel section in Getting started states:
Which is not completely true, as it only sets
process.env.NODE_ENV
to true if it was not defined before which is a small but significant difference which caused a huge issue in our projectTo Reproduce
See https://github.com/facebook/jest/blame/2af1c62750917d31b9d3b5d31ae2db8d3316414c/docs/GettingStarted.md#L110
Expected behaviour
Documentation should clearly state, that
process.env.NODE_ENV
is only set totest
if it was not set beforeThe text was updated successfully, but these errors were encountered: