-
-
Notifications
You must be signed in to change notification settings - Fork 6.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
config path cli option #3152
Comments
I'm not sure I understand this feature request, especially in terms how how it's different to #3150 and what the usecase is. Also, what's the error/issue happening right now? |
@Globegitter , FYI you can do it by: VUE_CLI_CONTEXT=/path/to/your/dir /path/to/your/dir/node_modules/.bin/vue-cli-service build Emm, It's not documented though. |
I worked together with @Globegitter on integrating vue-cli properly with bazel, so maybe I can shed some light. |
@Globegitter @DoHe Looks like you were on the right track, and thanks @jkzing for the tip indeed! Are you still planning to push your PR forward? FWIW I cooked up my own small wrapper for now. |
What problem does this feature solve?
In some way this relates to #3150, but even more generically, sometimes the
vue-cli-service
cli is executed in a different working directory than the config is located, so it would be greate if it was possible to pass the custom location of the config in. This would unblock our usage with bazel.What does the proposed API look like?
I would say
vue-cli-service -c path/vue.config.js
is quite common for such a flagThe text was updated successfully, but these errors were encountered: