public_git
/
nexus-vagrant
mirror of https://github.com/rgl/nexus-vagrant.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

mention that we can also use the NPM_TOKEN environment variable when publishing package

This commit is contained in:
Rui Lopes 2019-05-21 22:10:03 +01:00
parent 595ce6a0db
commit f31970d059
2 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
provision/use-npm-repository.sh
View File

@ -64,6 +64,8 @@ npm_auth_token=$(NODE_PATH=$PWD/node_modules node --use-openssl-ca /vagrant/prov
npm set //$nexus_domain/repository/npm-hosted/:_authToken $npm_auth_token npm set //$nexus_domain/repository/npm-hosted/:_authToken $npm_auth_token
# publish. # publish.
# NB instead of using the token from the npm configuration you can
# export the NPM_TOKEN environment variable.
npm publish --registry=$NPM_REGISTRY npm publish --registry=$NPM_REGISTRY
popd popd

2
provision/windows/use-npm-repository.ps1
View File

@ -90,6 +90,8 @@ $npmAuthToken = node --use-openssl-ca /vagrant/provision/npm-login.js 2>$null
npm set "//$nexusDomain/repository/npm-hosted/:_authToken" $npmAuthToken npm set "//$nexusDomain/repository/npm-hosted/:_authToken" $npmAuthToken
# publish. # publish.
# NB instead of using the token from the npm configuration you can
# set the NPM_TOKEN environment variable.
npm publish --registry=$env:NPM_REGISTRY npm publish --registry=$env:NPM_REGISTRY
popd popd