I installed Nexus Repository Manager OSS 3.2.1 and ran it on local machine.
I have three NPM repositories defined in Nexus:
In Settings/Security/Realms I've added npm Bearer Token Realm.
I can download packages from [PUBLIC], which works as intended.
.npmrc
registry=http://localhost:8081/repository/PUBLIC
npm install react // works fine, downloads from [PUBLIC]
I can download packages from [NPM], which works as intended.
.npmrc
registry=http://localhost:8081/repository/NPM
npm install react // works fine, downloads from [PUBLIC]
It won't work with [PRIVATE], because I don't have package named react.
I don't want to publish to [PUBLIC].
I can publish packages to [PRIVATE], which works as intended.
.npmrc
registry=http://localhost:8081/repository/PRIVATE
npm publish // works fine, publishes to [PRIVATE]
I can't publish packages to [NPM] and this is weird.
.npmrc
registry=http://localhost:8081/repository/NPM
npm publish // fails, should publish to [PRIVATE]
// gets HTTP 400
Detailed log: https://pastebin.com/5GuqNNhf
I understand that I can set up different url for publishing packages with publishConfig in package.json file, but for me it's duplicating configuration.
Can this be done with Nexus group repository?
You can't publish to a group repository. Change the URL you are using to the URL of a hosted npm repository, that will work.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With