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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 7, 2021. It is now read-only.
I have a scenario where I need to make 3 different builds with different configs:
Developer build, use developer endpoint
QA build, use QA endpoint and --release flags
Prod build, use prod endpoint and --release flags
This is not going to be possible with the way ns-bundle is currently set up.
One solution would be to allow a different webpack.*.js path to be passed in to ns-bundle.
Another solution is for ns-bundle to parse --env.abc flags and pass them directly to webpack.config.js. In webpack.config it's then possible to do different things based on what env flags are set.
I'm not a heavy webpack user, so I'm not sure what the ideal solution is here.
The text was updated successfully, but these errors were encountered:
I have a scenario where I need to make 3 different builds with different configs:
This is not going to be possible with the way ns-bundle is currently set up.
One solution would be to allow a different webpack.*.js path to be passed in to ns-bundle.
Another solution is for ns-bundle to parse --env.abc flags and pass them directly to webpack.config.js. In webpack.config it's then possible to do different things based on what env flags are set.
I'm not a heavy webpack user, so I'm not sure what the ideal solution is here.
The text was updated successfully, but these errors were encountered: