Skip to content
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

Error: Using `babel-preset-react-app` requires that you specify `NODE_ENV` or `BABEL_ENV` #2377

Closed
nicklayb opened this Issue May 26, 2017 · 18 comments

Comments

Projects
None yet
7 participants
@nicklayb
Copy link

nicklayb commented May 26, 2017

Can you reproduce the problem with latest npm?

yes

Can you still reproduce it?

yes

Description

When creating a new react app with create-react-app without doing anything, only running yarn start gives the following error :

Failed to compile.
./src/index.js
Module build failed: Error: Using `babel-preset-react-app` requires that you specify `NODE_ENV` or `BABEL_ENV` environment variables. Valid values are "development", "test", and "production". Instead, received: "undefined".
 (While processing preset: "/Users/nboisvert/Git/memberzone/node_modules/babel-preset-react-app/index.js")
    at Array.map (native)

Expected behavior

Run the template React app

Actual behavior

Displays :
image

Environment

Run these commands in the project folder and fill in their results:

  1. npm ls react-scripts (if you haven’t ejected):
memberzone@0.1.0 /Users/nboisvert/Git/memberzone
└── react-scripts@1.0.6
  1. node -v:
    v6.2.1
  2. npm -v:
    4.6.1

Then, specify:

  1. Operating system:
    macOS Sierrra 10.12.5
  2. Browser and version:
    Google Chrome Version 58.0.3029.110 (64-bit)

Reproducible Demo

Didn't add anything. Fresh install

@nicklayb

This comment has been minimized.

Copy link
Author

nicklayb commented May 26, 2017

Manage to resolve it by adding it to the .zshrc file, I've never had this before. I added the following :

export NODE_ENV=development
export BABEL_ENV=$NODE_ENV

And it works as expected, hope it could helps others!

Note from maintainers: this is not a good fix because it will build your production projects in development mode. Don’t do it! Instead subscribe to this issue and provide more details about your system if you experience this.

@nicklayb nicklayb closed this May 26, 2017

@gaearon

This comment has been minimized.

Copy link
Member

gaearon commented May 26, 2017

Hmm this doesn't sound right at all. You shouldn't need to set anything, and in fact setting them like this can create later issues.

@gaearon gaearon reopened this May 26, 2017

@gaearon

This comment has been minimized.

Copy link
Member

gaearon commented May 26, 2017

We are forcefully setting NODE_ENV to development from node_modules/react-scripts/scripts/start.js. I've never seen it getting reset after this.

@gaearon

This comment has been minimized.

Copy link
Member

gaearon commented May 26, 2017

Can you try deleting node_modules, running npm install and then trying again?
How do you run the app?

@cwissy

This comment has been minimized.

Copy link

cwissy commented May 27, 2017

same problem as @nicklayb - the .zshrc solution worked for me too 😄 . Deleting node_modules and re-npm-installing had no effect. Running the app through npm start

@AndrewBastin

This comment has been minimized.

Copy link

AndrewBastin commented May 27, 2017

I am also facing the same issue... It's in Windows though...
@nicklayb's solution worked for me as well on git bash....

@gaearon

This comment has been minimized.

Copy link
Member

gaearon commented May 27, 2017

I'm worried that if you just add this to your rc files you'll get development builds from production too. This is not the right solution and will give you builds many times bigger than they should be.

Can you investigate why a variable set in that script "disappears" by the time that Babel preset executes? We really need more information here because I can't reproduce it. The suggested solution in this thread is dangerous and you should not do it but instead I encourage you to try to diagnose the issue.

@gaearon

This comment has been minimized.

Copy link
Member

gaearon commented May 27, 2017

Everybody who has this problem, please could you share:

  • your node version
  • your shell
  • your OS
  • whether this reproduces in a different shell (eg if you are a zsh user try bash)
  • whether this reproduces both for npm start and npm run build

@gaearon gaearon changed the title New problem with NODE_ENV and BABEL_ENV Error: Using `babel-preset-react-app` requires that you specify `NODE_ENV` or `BABEL_ENV` May 27, 2017

@gaearon gaearon added the issue: bug label May 27, 2017

@AndrewBastin

This comment has been minimized.

Copy link

AndrewBastin commented May 27, 2017

I understand... I am currently using this as only a temporary hack...

Node Version : v7.9.0
Shell: Powershell (and Git Bash)
OS : Windows 10 (Anniversary Update)
The issue has so far popped up in Git Bash and Powershell (presumably cmd as well)..
Though on Git Bash I used the solution above as a workaround to get through...
npm start was affected... npm run build failed to run once for me but ran the second time... The generated production build was fine and did not show any errors as well (All done in Powershell)

@gaearon

This comment has been minimized.

Copy link
Member

gaearon commented May 27, 2017

Can you please remove the hack, verify it still fails on npm start, and then add this line to node_modules/react-scripts/scripts/start.js:

// ...
process.on('unhandledRejection', err => {
  throw err;
});

process.env.NODE_ENV = 'development';
+process.env.BABEL_ENV = 'development';

at about line 20, and try npm start again?

@AndrewBastin

This comment has been minimized.

Copy link

AndrewBastin commented May 27, 2017

Yay... That fixed it 😄

@gaearon

This comment has been minimized.

Copy link
Member

gaearon commented May 27, 2017

Can you post the exact message you were seeing before the fix? Did it also say "Instead received: undefined" or something else?

@AndrewBastin

This comment has been minimized.

Copy link

AndrewBastin commented May 27, 2017

/src/index.js
Module build failed: Error: Using babel-preset-react-app requires that you specify NODE_ENV or BABEL_ENV environment variables. Valid values are "development", "test", and "production". Instead, received: "undefined". (While processing preset: "C:\Users\Andrew Bastin\Desktop\test\node_modules\babel-preset-react-app\index.js")
at Array.map (native)

@gaearon

This comment has been minimized.

Copy link
Member

gaearon commented May 27, 2017

That's great, thanks.

@gaearon

This comment has been minimized.

Copy link
Member

gaearon commented May 27, 2017

Please try react-scripts@1.0.7 (or create a new project).
Should hopefully fix the issue.

https://github.com/facebookincubator/create-react-app/releases/tag/v1.0.7

@gaearon gaearon added this to the 1.0.7 milestone May 27, 2017

@1beb 1beb referenced this issue Jul 4, 2017

Closed

Fails to compile #4

@Ethan-liao

This comment has been minimized.

Copy link

Ethan-liao commented Aug 17, 2017

Adding "+process.env.BABEL_ENV = 'development';" worked for me too :)

@heshamelmasry77

This comment has been minimized.

Copy link

heshamelmasry77 commented Nov 23, 2017

to fix this you need to do that :
create a .babelrc file and then add this following code in it.

{
  "presets": [
    "react",
    "es2015",
    "stage-2"
  ]
}

i am using es2015 and stage-2 and for your : scripts : start.js add this :

process.env.BABEL_ENV = 'development';
process.env.NODE_ENV = 'development';

you can create a development , test, build one. my advice to you and i found that it is good to understand what is happening is to eject the react project.

@English3000

This comment has been minimized.

Copy link

English3000 commented May 13, 2018

What's the fix for a non-CRA app that uses babel-preset-react-app?

Already tried adding to plugins: [ new webpack.EnvironmentPlugin({ NODE_ENV: 'development' }) to no avail.

Update: My workaround was to simply switch to babel-preset-react config.

@lock lock bot locked and limited conversation to collaborators Jan 19, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.