Pass additional arguments to yarn

[andreyfel]

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.

[kategengler]

npmOptions should be used with useYarn as well. Can you run with DEBUG=ember-try* <your ember-try command> to get output that will tell us what command is being run?

[kategengler]

@andreyfel Is this still happening?

[oliverlangan]

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 DEBUG=... command, this is the yarn command that was run:

yarn install --ignore-optional --no-lockfile --ignore-engines

That said, it still installed optionalDependencies in a sub-package, at least on our CI environment.

(Recent releases of ember-lodash use optionalDependencies if you are looking for a package with which to test.)

[rwjblue]

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.