rfcs
rfcs copied to clipboard
Public change requests/proposals & ideation
Proposal to implement more robust lifecycle scripts with reify context. See issue npm/cli#3042
## Motivation ("The Why") Based on the discussion on npm/cli#564, npm/feedback/discussions/340 and a few other issues. The purpose of this proposal is to offer a middle ground between `npm install`...
Following discussion on #477 and previously on #463, workspaces that depend on sibling workspaces via the `file:` protocol (a.k.a. linked or symlinked dependencies) should run the sibling workspaces' `prepare` scripts...
### The problem When running "NPM audit" with alias packages, or packages received from git installation, it simply skips the package with no warning or sign that the package was...
## Motivation ("The Why") We are encountering this issue in Vite: https://github.com/vitejs/vite/issues/6210 In summary: - **Background**: Vite bundles most of its dependencies with Rollup. Therefore, its `LICENSE.md` includes all the...
## Motivation ("The Why") npm 7 introduced a change where it computes tarball URLs from the registry name instead of using the URL provided by the registry. This causes third...
## Motivation `node_modules` often contains a lot of files that change frequently, which can significantly slow down backup solutions like Time Machine, so it would make sense to exclude them...
## Motivation ("The Why") It's super useful, in npm we have to run `npx npm-check -u` that's a third party package. ### Example Try it in yarn. ### How ####...
## Motivation ("The Why") My company uses CD to publish our internal npm packages. However, the publish job, if ran twice, will error the second time, because the package is...