snippetreactCritical
create react app not picking up .env files?
Viewed 0 times
createappreactnotfilespickingenv
Problem
I am using create react app to bootstrap my app.
I have added two
My
When I run my app using
I've tried different things, but its just not picking up the veriables in my development file, what am I doing wrong?!
Directry structure is:
Package.json script is:
Edit:
@jamcreencia correctly pointed out my variables should be prefixed with
Edit 2
It works okay if I name the file
I have added two
.env files .env.development and .env.production in the root.My
.env.development includes:API_URL=http://localhost:3000/api
CALLBACK_URL=http://localhost:3005/callbackWhen I run my app using
react-scripts start and console out process.env it spits out{ NODE_ENV: "development", PUBLIC_URL: "" }I've tried different things, but its just not picking up the veriables in my development file, what am I doing wrong?!
Directry structure is:
/.env.development
/src/index.jsPackage.json script is:
"start": "export PORT=3005; npm-run-all --parallel server:start client:start",
"client:start": "export PORT=3005; react-scripts start",
"server:start": "node server.js",
"build": "react-scripts build",Edit:
@jamcreencia correctly pointed out my variables should be prefixed with
REACT_APP.Edit 2
It works okay if I name the file
.env but not if I use .env.development or .end.productionSolution
With create react app, you need to prefix
** Make sure your .env file is in the root directory, not inside src folder.
CRA Docs on Adding Custom Environment Variables:
Note: You must create custom environment variables beginning with
REACT_APP_ to the variable name. ex:REACT_APP_API_URL=http://localhost:3000/api
REACT_APP_CALLBACK_URL=http://localhost:3005/callback
** Make sure your .env file is in the root directory, not inside src folder.
CRA Docs on Adding Custom Environment Variables:
Note: You must create custom environment variables beginning with
REACT_APP_. Any other variables except NODE_ENV will be ignored to avoid accidentally exposing a private key on the machine that could have the same nameContext
Stack Overflow Q#48378337, score: 650
Revisions (0)
No revisions yet.