-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Separate dev/prod configs #182
Comments
I have this and #174 done locally. I'm trying to make it easier and I may end up making 3 webpack configs |
@gdi2290 Many thanks for your prompt response and action! Looking forward to pulling this change. |
done via cf4b3f2...master |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Can we add separate dev/prod config settings which apply depending on context?
Currently production settings need to be commented out (debug:true) or changed (devtool: 'eval') in webpack.config between dev/prod scenarios. This is not ideal.
There are two prevalent solutions for separate webpack dev/prod configs.
(1) Using npm webpack-merge and environment variables to TARGET dev/prod in same config file. SurviveJS implementation
(2) Using two separate webpack.config files for dev/prod. This is more common solution on most projects I have studied.
The text was updated successfully, but these errors were encountered: