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 1.12.1 creates .bin folders inside dependency folders #6622
Comments
I think I just ran into this as well. After upgrading to 1.12.1 (from 1.10.1) and running
When I look at the file in question, I see a symlink into my cache, which seems wrong:
And that symlinks to itself, hence the loop:
If I downgrade to 1.10.1, the problem goes away and |
Interesting - can you open a PR to add a breaking test case to Yarn? I'll see to fix it in the next patch release |
@arcanis I cannot allocate time to dive into the project's infrastructure to report an issue. If it wasn't a work project, I would like to :) We will just use an older version until then. |
Will be fixed by #6628, which will likely land in the next patch release. |
Because of this issue, I got an error when generating APK release from React Native project. |
I have been experiencing this issue on Windows boxes as well. This is not specific to UNIX based OS. The problem was a bit harder to determine on Windows though. When packaging the final apps, the symlinks couldn't be copied and the error message reported by windows was misleading. |
1.12.1
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Installing a dependency with a binary not only adds a
.bin
to node_modules, but also to the dependencies own folder.This did not happen in yarn 1.10.1.
If the current behavior is a bug, please provide the steps to reproduce.
node_modules/.bin
). Suppose for example markedyarn
node_modules/marked/
there will be a.bin
folder.What is the expected behavior?
Dependencies should not have
.bin
folders with extra symlinks.Please mention your node.js, yarn and operating system version.
node: 8.12.0 (also tried 8.11.3)
yarn: 1.12.1
OS: Ubuntu 18
I tried the error on multiple ubuntu and debian container images.
EDIT: I thought this was only occurring inside containers, but it turns out only the containers were updated. I suspect this just broke in the newest 1.12
The text was updated successfully, but these errors were encountered: