yarn install --production does not install dependencies that are transitive dependencies of a dependency and a dev dependency

Created on 29 Nov 2016 · 6Comments · Source: yarnpkg/yarn

What is the current behavior?

When a package is depended on by both a dependency and a devDependency, the devDependency visibility takes precedence when installing into production, this results in shared dependencies not being installed in production.

If the current behavior is a bug, please provide the steps to reproduce.
https://github.com/dreid/yarn-dev-dep-failure

yarn install --production does not install function-bind

npm install --production does install function-bind

What is the expected behavior?

Production builds should install dependencies that are visible from production dependencies.

Please mention your node.js, yarn and operating system version.

❯ yarn --version
0.17.9
❯ node -v
v7.1.0
❯ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.12.1
BuildVersion:   16B2555

cat-bug

Source

dreid

👍7

Most helpful comment

@bestander on it!

itamararjuan on 1 Dec 2016

👍4

All 6 comments

Making it higher priority, thanks

bestander on 1 Dec 2016

👍2 😄1

@bestander are you fixing this yourself ?
was thinking of helping solve this as it's totally preventing me from moving some of my services to yarn.

itamararjuan on 1 Dec 2016

@itamararjuan, I would totally appreciate if you fix this.
It may take some time for me to get to this one.
Please don't forget to include a test

bestander on 1 Dec 2016

@bestander on it!

itamararjuan on 1 Dec 2016

👍4

Looks like this was fixed with #2116, it required significant refactor to how we do package visibility. Sorry @itamararjuan, didn't realise that the issue I was fixing was so pathalogical and extended to this case too.

sebmck on 2 Dec 2016

hey sebastien
no worries thanks for doing so much for everybody. this is an awesome
project. if help is needed dont hesitate to ping and I'll do my best to
help with other issues :)

On Fri, Dec 2, 2016, 13:10 Sebastian McKenzie notifications@github.com
wrote:

Looks like this was fixed with #2116
https://github.com/yarnpkg/yarn/pull/2116, it required significant
refactor to how we do package visibility. Sorry @itamararjuan
https://github.com/itamararjuan, didn't realise that the issue I was
fixing was so pathalogical and extended to this case too.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/yarnpkg/yarn/issues/2073#issuecomment-264431011, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFr4O5bqcN-8tF9JwStcRsRmbTB2EteOks5rD_yfgaJpZM4K_R_l
.