-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Pass additional arguments to yarn #188
Comments
|
@andreyfel Is this still happening? |
I can verify that npmOptions are being passed to yarn. Note that '--no-optional' is the npm flag, while '--ignore-optional' is the yarn flag. Using the above
That said, it still installed optionalDependencies in a sub-package, at least on our CI environment. (Recent releases of |
FWIW #409 made it possible to control exactly what is passed in to each of the dependency managers. I'm going to close now, but if folks still think this is a bug I'm happy to reopen. |
I need to skip optional dependencies on the yarn install phase to reduce time of the build. So, I need to run yarn install with "--ignore-optional" argument.
Generic solution for this issue would be to be able to configure yarn options.
I tried to use npmOptions parameter from the ember-try config but seems it is not respected when useYarn is set to true.
The text was updated successfully, but these errors were encountered: