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
I've seen this issue a few times. Basically the user have a yo version installed, and their npm now install in a different binary folder. This cause an issue where the user always use the old yo version as their new ones is not found on their path.
I'm unsure how we could detect this, but the issue is clear when you check where npm installs modules against what is returned with which yo (where yo on windows)
This is really a problem with npm. I don't see a way to test for this as the user could have it setup like that. This is really more of a npm issue. If we try to be too smart about fixing this, it could have adverse affects.
I've seen this issue a few times. Basically the user have a
yo
version installed, and their npm now install in a different binary folder. This cause an issue where the user always use the old yo version as their new ones is not found on their path.I'm unsure how we could detect this, but the issue is clear when you check where npm installs modules against what is returned with
which yo
(where yo
on windows)Related bug reports on our trackers
The text was updated successfully, but these errors were encountered: