-
-
Notifications
You must be signed in to change notification settings - Fork 60
New Yarn version, package.json bin causes warning #64
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
Comments
I do not see warning...
|
You're right I narrowed it down to just yarn v1.21.1.
When the cache isn't cleared, the warning doesn't show up next time. Even in a fresh directory. |
So the fix will be remove bin at all or change package.json to?
|
I'm not certain about the fix, just happened to encounter this in the wild. It shouldn't be required by the security patch to remove it entirely though. Especially locally like we're doing here a properly formatted bin is expected to work. |
With the recent security changes:
https://blog.npmjs.org/post/189618601100/binary-planting-with-the-npm-cli
It causes a warning
The text was updated successfully, but these errors were encountered: