Details
Description
Start with this repository setup:
npm-group --- npm-hosted1 --- npm-hosted2
Configure your registry for *gets* to point at npm-group with proper permissions.
Using npm publish and a proper publishConfig url in package.json
deploy package X version 0.0.1 to npm-hosted1
deploy package X version 0.0.2 to npm-hosted2
Execute npm view X versions
This returns one version 0.0.1.
Reorder the group members:
npm-group --- npm-hosted2 --- npm-hosted1
Execute npm view X versions
This returns one version ( 0.0.2 ).
Expected
- npm view X versions should list all versions of the same package in all group members
Notes:
- NPM groups do not exactly match up with Maven groups
- NPM packages are flat, there is no hierarchy
Because of this, should we treat NPM groups like Maven groups?
We have a concern that we could merge packages together due to the flat nature of NPM that weren't meant to be merged
Scoped packages was invented to circumvent this problem
Potentially do:
- Allow for capability for specific groups to do merge, and instruct the users on how to add hosted/proxy repos to the group
Attachments
Issue Links
- is related to
-
NEXUS-6857 Support for npm scoped packages
-
- Closed
-
- relates
-
NEXUS-11290 provide option to suppress merging metadata for the same npm package in different group members
-
- Done
-
- mentioned in
-
Page Loading...