Package Exports

dcs-catalyst-commons
dcs-catalyst-commons/dist/index.js
dcs-catalyst-commons/dist/types
dcs-catalyst-commons/dist/types.js

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 (dcs-catalyst-commons) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

catalyst-commons

Common tools and types to share between catalyst servers and clients

Contributing

Build and test

npm install
npm run build
npm run test

Releases

Stable Releases

To publish a new release, a tag following SemVer must be done in master branch following the format: MAJOR.MINOR.PATCH and that will trigger a Github Workflow that publishes the new version of the library, tagging it as latest.

Master Releases

Every commit to master branch triggers a NPM Publish with the beta version following the convention NEXT_MAJOR.NEXT_MINOR.NEXT_PATCH-TIMESTAMP.commit-COMMIT_SHA, tagging it as next.

Tag Releases

If you need to publish a NPM package in a work in progress commit, then you can create a git tag, and that will trigger an automatically NPM publish following the convention NEXT_MAJOR.NEXT_MINOR.NEXT_PATCH-TIMESTAMP.commit-COMMIT_SHA and tagging it on NPM with your custom tag: tag-CUSTOM_TAG.