Publish NPM packages
The DTaaS software is developed as a monorepo with multiple npm packages.
Default npm registry
The default registry for npm packages is npmjs. The freely-accessible public packages are published to the npmjs registry. The publication step is manual for the runner.
At least one version of runner package is published to this registry for each release of DTaaS.
The publication step for library microservice is automated via github actions.
Github npm registry
The Github actions of the project publish packages. The only limitation is that the users need an access token from Github.
Private Registry
Setup private npm registry
Since publishing to npmjs is irrevocable and public, developers are encouraged to setup their own private npm registry for local development. A private npm registry will help with local publish and unpublish steps.
We recommend using verdaccio for this task. The following commands help you create a working private npm registry for development.
You can open http://localhost:4873
in your browser, login with
the user credentials to see the packages published.
Publish to private npm registry
To publish a package to your local registry, do:
The package version in package.json gets updated as well. You can
open http://localhost:4873
in your browser, login with the user credentials
to see the packages published. Please see
verdaccio docs
for more information.
If there is a need to unpublish a package, ex: @dtaas/runner@0.0.2
, do:
To install / uninstall this utility for all users, do:
Use the packages
The packages available in private npm registry can be used like the regular npm packages installed from npmjs.
For example, to use @dtaas/runner@0.0.2
package, do: