Gar
Gar
The unrelated changes to new lines is making this harder to review than it needs to be. Please limit changes only to what are needed.
Thanks for this submission but I think we will leave it as-is.
No apology needed. Thank you for submitting this, don't let this discourage you from future contributions.
This behavior belongs in pacote. It's already doing a lot of logic to pick the right manifest based on the spec. If fact it may actually be `npm-pick-manifest` that needs...
This is a subtle one. npm itself includes the `latest` tag when choosing a version from a range to determine what version to install. If today you were to set...
Yes I believe that's what would happen. The `latest` is picked in the absence of an extant version in the tree. If the extant version satisfies the semver range it...
This looks pretty similar to https://github.com/npm/cli/pull/7579. Is this a similar root cause? In any event this will needs tests showing how to get into this broken state and show how...
> we just refactor this to download via fetch Unless the package manager in question bundles its dependencies, the only way for you to do this is to in fact...
Thanks @GeoffreyBooth, this is not an easy conversation to be late into joining. I appreciate your help in fielding my basic questions. I don't have much to add then at...
> I wish we could catch these. It is not possible to test this kind of code that uses cwd /. We don't "support" running out of root, and there...