-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
yarn install --production misses some required transitive dependencies #2263
Comments
Could you check in yarn 0.18.1? |
It's much closer to being correct, but still fails on one of the transitive dependencies:
|
Indeed, I can reproduce, looks like we are missing this path for the example package.json:
|
Here's a discussion that is relevant to this issue: heroku/heroku-buildpack-nodejs#337 And if it helps, here's a diff of what got installed after running EDIT: #761 seems to be relevant as well. |
This seems related to: I've been pinging them to re-open but haven't gotten a response yet. |
The minimum reproducible package.json is:
New |
I can still repro the above issue in latest master:
|
Same issue as #2141 as already said upper. So #2141 should not be closed. Still an issue with 0.19.1. And I can provide another very simple package.json and steps to reproduce:
Result:
Without --prod, everything is ok:
Ok also using --prod but removing the devDependency in package.json:
Result:
Hope it can helps to fix that definitely! |
Also having this issue same as reported by @ebaynaud
Seem like this fixes it
But this should not be required :(. |
Should be fixed in master now, will be released in 0.20 next week |
…2468, yarnpkg#2263 (yarnpkg#2537) * Explicitly mark ignored deps of non-ignored packages as non-ignored (yarnpkg#761, yarnpkg#2468, yarnpkg#2263) * Fix style nits
Running
yarn install
works fine.yarn install --production
should also work, installing only those dependencies needed outside of dev, but it misses some transitive dependencies that are present in thedevDependencies
section.Steps to reproduce
package.json
:node_modules
directory exists.yarn.lock
if it already exists.yarn install --production
.Expected behavior
Running
npm list --production
(as done in the postinstall script) should report no missing dependencies.Actual behaviour
Several transitive dependencies are missing. e.g.,
error-ex@^1.2.0
,minimist@0.0.8
, and others.Notes
This behaviour is consistent regardless of whether the lockfile is present before running the command.
Please mention your node.js, yarn and operating system version.
Using Yarn 0.18.0, Node.js v6.7.0, OSX 10.12.1 (Darwin Kernel Version 16.1.0: Thu Oct 13 21:26:57 PDT 2016; root:xnu-3789.21.3~60/RELEASE_X86_64), and zsh.
The text was updated successfully, but these errors were encountered: