Gar
The functionality for these was moved into the workspaces in npm that are all published as separate packages on the npm registry. The biggest barrier right now for folks using...
Given how in-depth a true documentation of `exports` needs to be, I second the idea of linking to [Node's documentation on this](https://nodejs.org/api/packages.html#exports). Node is what is parsing that field, not...
Where are you seeing this? What command are you running? I can not reproduce this ```sh ~/D/n/s/triage $ npm i added 1 package, and audited 2 packages in 2s found...
Tags make no difference either ```sh ~/D/n/s/triage $ npm i added 1 package, and audited 2 packages in 2s found 0 vulnerabilities ~/D/n/s/triage $ npm pkg get dependencies { "@gar/promisify":...
This is going to need tests
The edge's `reload` seems to me where this kind of thing should be happening. Is this a more subtle error perhaps where we're not reloading the overrides where we should?
> Anything else we need to do to merge this? Just patience. Holidays are over and we got a lot of PRs. This PR is on the work board it's...
Historically npm has normalized that entry when publishing a package, which lead to a discrepancy between what was in the package.json and what was in the manifest on the registry....
`npm ci` installs a package as a dependency of the global namespace. It is fundamentally different than installing the dependencies for a package. There is no global package.json, so there...
[BUG] Update command gets `workspaces <package name> in filter set, but no workspace folder present`
Command succeeds just fine, just an erroneous log message