Pete Gonzalez

@kenotron @scsewall @jbcpollak

Sure! @zkat this would be the **absolute most valuable** issue for NPM to help us out with: > - We need to a workaround for the NPM's regression with installing...

When I tried workaround #2 again just now with the latest NPM 6.4.1, it's crashing with this call stack: ``` Unhandled rejection Error: invalid config key requested: errors at BadKeyError...

In this case the **package-lock.json** was created by the same version of NPM. (This was an isolated manual repro, not a real Rush installation.)

> hey, y'all! I'd love to help out here with any questions y'all have (though I've got pretty low availability lately). One thing to note: npm is [moving away from...

> I'll also note that I don't believe anything having issues with `npm@5` is worth fixing: we no longer support that version, and we won't be doing any additional releases...

We don't really recommend one of the package managers as being "best". The decision depends on your needs. But I believe the Rush docs call out some non-subjective considerations: -...

Status update: NPM recently announced that version 7 will finally provide support for monorepos. Today, the monorepo support implemented by Yarn and PNPM is already reasonably close to what we...

@NikitaIT Could you share a repro of your build that failed using PNPM? I've heard from several people that `vue-cli` does not correctly declare its imports, making it incompatible with...

BTW I've opened this issue to track the feature to enable Rush to use the package manager's monorepo support (workspaces): https://github.com/microsoft/rushstack/issues/1553