You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Honestly this seems like intentional behaviour, I don't think we should do anything explicitly to detect a yarn install command since we don't know the location of the original binary and any detection will be sloppy. install is a valid lifecycle script hook and we're executing it correctly, there's nothing being ignored.
@kittens I was really confused by your response until I googled "npm lifecycle scripts" and came across this.
I actually didn't know that install was a special thing that was supposed to run after yarn/npm install -- I thought it was just a regular script. I didn't know it would be triggered automatically after a yarn install; I just wanted to run it manually via yarn run install.
In that case, this does make perfect sense. Sorry @wyze and @thejameskyle -- thank you for taking my issue report seriously, but I think @kittens is actually right here. This was due to my own misunderstanding. I don't think you need to try to detect this situation.
yarnpkg
locked as resolved and limited conversation to collaborators
Oct 23, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Do you want to request a feature or report a bug?
Bug
If the current behavior is a bug, please provide the steps to reproduce.
Add this to your
package.json
:Run
What is the current behavior?
What is the expected behavior?
No infinite loop. Perhaps copy what Composer does: emits this warning:
And then carries on with the built-in command.
Please mention your node.js, yarn and operating system version.
Node: v6.3.1
Yarn: 0.16.0
OS: Win10 Anniversary
The text was updated successfully, but these errors were encountered: