Gar
Gar
Closing due to age. If this is still something you want feel free to rebase against the `HEAD` branch and be sure test are passing. The name of the attribute...
This looks like a similar PR to https://github.com/npm/npm-package-arg/pull/49. I think either one would be ok w/ tests, docs, and a proper attribute name.
Closing due to age. If this is still something you want feel free to rebase against the `HEAD` branch and be sure test are passing. The name of the attribute...
Erring on the side of caution and making it a major for this package, and introducing it in npm9.
After landing #97 I am going to close this. During the cleanup to get tests in npm working for this change I found cases where we are relying on this...
You betcha. I think the most logical initial place to start would be in arborist, where we parse the `add` directive, i.e. `add-rm-pkg-deps.js`. I'd also wait a day or two...
Nope, check out the rest of the comment. > npm (via npm-pick-manifest) will prefer its default tag if given a range that includes it
Converting to draft while I do the next phase, which is to `npm link` this into the cli and smoke test it.
This is a known problem with a proposed PR [here](https://github.com/npm/cli/pull/3653). Not sure if removing the original "description" is the solution here though.