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
We are using bazel (https://bazel.build/) as a build system in a monorepo setup. Bazel usually executes in the root of the monorepo but we still have a package.json per project, so it might be in app1/package.json as well as app2/package.json. Adding the resolveFrom in the root package.json does not work for this use-case as depending on which project I point I need to point the cli at the different directory. So if I could just specify vue-cli-service --resolve-from appX that would solve my issue as I can change that per invocation and I can even tell bazel to add different cli flags when running it for different aps..
What does the proposed API look like?
It would do the same as the existing resolveFrom attribute just allowing to set this via a cli arg. Alternatively setting this via en environment variable could also solve our issue, but in not such a nice fashion.
The text was updated successfully, but these errors were encountered:
What problem does this feature solve?
We are using bazel (https://bazel.build/) as a build system in a monorepo setup. Bazel usually executes in the root of the monorepo but we still have a package.json per project, so it might be in
app1/package.json
as well asapp2/package.json
. Adding theresolveFrom
in the root package.json does not work for this use-case as depending on which project I point I need to point the cli at the different directory. So if I could just specifyvue-cli-service --resolve-from appX
that would solve my issue as I can change that per invocation and I can even tell bazel to add different cli flags when running it for different aps..What does the proposed API look like?
It would do the same as the existing
resolveFrom
attribute just allowing to set this via a cli arg. Alternatively setting this via en environment variable could also solve our issue, but in not such a nice fashion.The text was updated successfully, but these errors were encountered: