Skip to content

Feature request: Configurable path/name to webpack.config.js #5218

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

Closed
maxorlovsky opened this issue Sep 13, 2018 · 4 comments
Closed

Feature request: Configurable path/name to webpack.config.js #5218

maxorlovsky opened this issue Sep 13, 2018 · 4 comments
Assignees
Labels
Milestone

Comments

@maxorlovsky
Copy link

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

@maxorlovsky maxorlovsky changed the title Feature request: Configurable path to webpack.config.js Feature request: Configurable path/name to webpack.config.js Sep 13, 2018
@sis0k0
Copy link
Contributor

sis0k0 commented Sep 13, 2018

Great idea!

@rosen-vladimirov rosen-vladimirov transferred this issue from NativeScript/nativescript-dev-webpack Jan 16, 2020
@rosen-vladimirov rosen-vladimirov self-assigned this Jan 16, 2020
@rosen-vladimirov rosen-vladimirov added this to the 6.4.0 milestone Jan 16, 2020
@rosen-vladimirov
Copy link
Contributor

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

@dtopuzov
Copy link
Contributor

Available in nativescript-dev-webpack@next, will be officially shipped in [email protected]

@maxorlovsky
Copy link
Author

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants