-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
how can i set three env in the project #702
Labels
Comments
why the
set the env from the
|
Yeah, there are times where I need a development build. |
chances
added a commit
to chances/parcel
that referenced
this issue
Jun 22, 2018
…el-bundler#702 Like others in parcel-bundler#702, there are times when I need a development build. This change remedies that by using the `NODE_ENV` set by a user in the build command, but will default to `production` is none is provided.
This was referenced Jun 22, 2018
Fixed by #1600 |
devongovett
pushed a commit
that referenced
this issue
Oct 15, 2018
devongovett
pushed a commit
that referenced
this issue
Oct 15, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Choose one: is this a 🐛 bug report or 🙋 feature request?
🎛 Configuration (.babelrc, package.json, cli command)
🤔 Expected Behavior
I hope if i run
yarn run test
, i can build file with the config of test , because the url in test is different from production😯 Current Behavior
i see the cli file , if i have the command
build
, theNODE_ENV
will be set toproduction
,and onlydevelopment
andproduction
in the file , i hope get anothertest
💁 Possible Solution
🔦 Context
💻 Code Sample
🌍 Your Environment
The text was updated successfully, but these errors were encountered: