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
Currently webpack.config.js is hardcoded in projectFilesManager.js:60
It would be great if nativescript-dev-webpack could read path to a file / name of the webpack file from nsconfig.json or as an argument to cli, like it happening with webpack, where you can specify --config /other/path/different-webpack.config.js
The text was updated successfully, but these errors were encountered:
maxorlovsky
changed the title
Feature request: Configurable path to webpack.config.js
Feature request: Configurable path/name to webpack.config.js
Sep 13, 2018
In the current next version of CLI, you can set webpackConfigPath in your nsconfig.json. CLI will use the value and pass the path to --config option when starting the webpack process.
An example how to have a webpack configuration, that has a custom logic, can be found in this PR: NativeScript/nativescript-dev-webpack#1116
Currently webpack.config.js is hardcoded in projectFilesManager.js:60
It would be great if nativescript-dev-webpack could read path to a file / name of the webpack file from nsconfig.json or as an argument to cli, like it happening with webpack, where you can specify --config /other/path/different-webpack.config.js
The text was updated successfully, but these errors were encountered: