Skip to content
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

Install regression between 0.19.1 and 0.20.0 #2714

Closed
SomeoneWeird opened this issue Feb 17, 2017 · 2 comments
Closed

Install regression between 0.19.1 and 0.20.0 #2714

SomeoneWeird opened this issue Feb 17, 2017 · 2 comments
Labels

Comments

@SomeoneWeird
Copy link

SomeoneWeird commented Feb 17, 2017

Do you want to request a feature or report a bug?

Bug.

What is the current behavior?

Package skeletron fails to install.

If the current behavior is a bug, please provide the steps to reproduce.

Installation works w/ 0.19.1

➜ yarn --version
0.19.1
➜ yarn add skeletron
yarn add v0.19.1
warning No license field
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 📃  Building fresh packages...
success Saved 1 new dependency.
└─ skeletron@0.0.2
warning No license field
✨  Done in 0.72s.

Installation fails w/ 0.20.0 (also fails with latest stable 0.20.3 and latest prerelease 0.21.0)

➜ yarn --version
0.20.0
➜ yarn add skeletron
yarn add v0.20.0
warning No license field
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
error An unexpected error occurred: "ENOENT: no such file or directory, lstat '/private/tmp/node_modules/findit/test/symlinks/dir1/does-not-exist'".
info If you think this is a bug, please open a bug report with the information provided in "/private/tmp/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

What is the expected behavior?

Package skeletron successfully installs.

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

NodeJS 5/6/7

macOS 10.12.3 / Amazon Linux 2016.09

@SomeoneWeird
Copy link
Author

Looks like 65e89b5 is the culprit

@bestander
Copy link
Member

@SomeoneWeird, thanks for finding the cause, I'll follow up with #2744 now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants