Luke Karrys

I think this could be fairly robust if it used the npx specific cache, and/or known bins when done in a project directory.

Can there be an optional parent scope for a "config version"? It wouldn't be tied directly to the npm version but it would allow us to making breaking config changes...

@wraithgar This would be a good time to evaluate this change as we are on the verge of a major release of `pacote`?

They are somewhat accessible now but you're correct that they are mostly for internal use. Could you provide a code example of how you'd like to use them? It's possible...

This is working by design. The default value of `-i` is `patch` and invalid versions are filtered out of the input.

@mklement0 Thanks for the feedback. I closed this issue as a first pass through this repo, so maybe "by design" was the wrong choice of words. The code makes it...

I'm not opposed to this but I do think this would be a breaking change.

Reopening after some research into other issues. I think providing a supported way to do this without reaching into `range.set[][].operator` would be nice, similar to what was discussed for getting...

The engines of `readable-stream@^4` is incompatible with our engines for npm8. Let's revisit this with the release of npm 9.

One thing we should add to this is the ability to differentiate between directing to files vs directories. `hosted-git-info` currently only has the concept of a `treepath` for each host,...