This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
Stop inferring package names in directories w/o package.json files #9744
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Reviewed in person with @othiym23: 🐑 |
|
Landed in 3.3.5! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes: #9695
This fixes that issue because, on Windows, your globals directory is a
$APPDATA/npm. And of course, your globals directory doesn't have a package.json because's not a package. So previously we were intuiting its name, from directory name, which wasnpm, and then we tried to installnpmin and and "eek, those look identical!!"