nlf

confirmed bug, we're ignoring the `dev` flag in the `npm-shrinkwrap.json`, installing the dev dependencies and flagging them as `extraneous` when we write the `package-lock.json`. i confirmed the `npm-shrinkwrap.json` flags the...

> C:\Users\QQ370\AppData\Roaming\npm\node_modules\babel-cli\node_modules\[email protected]@babel-messages this path makes it appear as though you globally installed this package with either `pnpm` or `yarn@2` which both use a local store and symlinks to manage their...

> With this change, what difference do you see between peer deps and optional peer deps, in npm? 🤔 the same as the difference between `dependencies` and `optionalDependencies`, attempt to...

i've converted this pull request back to a draft to convey that it is only a proposal. we have a lot of things to consider before changing something like this.

i think one significant thing we can do here to help us avoid the concern about breaking things is to define what exactly the node team would like to ensure...

> Here is a non-exclusive list: > > 1. a `package-lock.json` file from the previous version of npm is left untouched after `npm install` this is the case if the...

`@npm` is a scope we often point to our private registry for internal services, and some of those services may also use the packages we would want to move there....

No, it's not, but there is a clear and distinct separation between modules that are only capable of working on npm related tasks and those that are valuable to anyone....

So we currently store the constructors at `this._collections`/`this._children`, but not the actual instances. In a roundabout way this will work for my purposes, but maybe storing references to the instances...

It being expensive is not a reason to not implement it. It's a reason to default it to off, but it doesn't mean we shouldn't have the option. As for...