Package Exports
- bulk-npm-publish
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (bulk-npm-publish) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Bulk NPM Publish
Publish Multiple NPM packages from verdaccio storage
Getting Started
- create
.envfile at the root directory - run
npm start - run the created script that been output
Environment file
create .env file for set the configuration
STORAGE_PATH=<storage-path> # (i.e 'C:\\Users\\<user-name>\\AppData\\Roaming\\verdaccio\\storage\\')
PUBLISH_SCRIPT_DEST_PATH=<script-path> # (i.e './publish-all.bat')
REGISTRY_URL=<registry-url> # (i.e 'http://localhost:4873')If no
REGISTRY_URLspecified it will will create script without the--registry=<registry-url>
Example output
STORAGE_PATH='C:\\Users\\<user-name>\\AppData\\Roaming\\verdaccio\\storage\\'
PUBLISH_SCRIPT_DEST_PATH='./publish-all.bat'
REGISTRY_URL='http://localhost:4873' # Verdaccio urlThe output is:
call npm publish C:/Users/<user-name>/AppData/Roaming/verdaccio/storage/@angular/cli/cli-7.3.9.tgz
call npm publish C:/Users/<user-name>/AppData/Roaming/verdaccio/storage/mime/mime-1.6.0.tgz
call npm publish C:/Users/<user-name>/AppData/Roaming/verdaccio/storage/ts-node/ts-node-7.0.1.tgzTest
Run npm test for testing