cli

cli copied to clipboard

Self Hosting 3rd party registries & adding/removing 3rd party registries into npm

8

- The ability to self host your own npm registries which will require releasing npm to be fully open source and instructions on how to deploy your own npm registry...

trymeouteh

[BUG] prepare script doesn't see node_modules bin executables

6

### Is there an existing issue for this? - [X] I have searched the existing issues ### This issue exists in the latest npm version - [X] I am using...

aovchinn

[BUG] Impossible to reliably passthrough NODE_OPTIONS in .npmrc

5

### Is there an existing issue for this? - [x] I have searched the existing issues ### This issue exists in the latest npm version - [x] I am using...

aczekajski

fix: issue #7892 prevent package-lock.json creation without package.json

4

fix for npm install creating package-lock.json file when accidentally run in the wrong directory in a project. ## References Fixes #7892

Kyle-Ignis

[BUG] peerDependencies of package behave like dependencies when package is locally installed

2

### Is there an existing issue for this? - [X] I have searched the existing issues ### This issue exists in the latest npm version - [X] I am using...

DanKaplanSES

Right now, when using `npm run --workspaces {cmd}` or `npm run -w {package1} -w {package2} {cmd}`, npm will always run the command in every single package even if some packages...

bralax

fix: omit name from package-lock.json in case of package.json don't have name

2

## References

kchindam-infy

[BUG] ERESOLVE error because only latest version in peer dependency range is respected in dep resolution

5

### Is there an existing issue for this? - [X] I have searched the existing issues Potentially related issues: - #4104: _almost_ the same but involves multiple direct dependencies -...

fischeversenker

fix(arborist): don't checkEngine/checkPlatform for extraneous deps

4

Fixes #7622 The linked issue describes the problem in detail, I won't replicate that here.

YodaDaCoda

[BUG] not installing peer dependencies for workspaces if they are not nested inside the root package

3

### Current Behavior: having 'library-project' with peer-dependencies adjacent to 'main-project' and 'main-project' with workspaces: ['../library-project'] (outside of 'main-project' folder) 'npm install' in 'main-project' is not installing the peer-dependencies example: ```...

talsi