Releasing a new version

• First, increase the version in package.json
• Run npm install to update dependencies

Then, make sure that the Commit Checklist is fullfiled.

• Check that tests run with 100% coverage
• Check and resolve any security issues
• Check if there are any code warnings
• Check that JavaScript documentation builds and is complete
• Check that your new features or fixed are documented and appear in the changelog
• Check that the client-side library builds and work

In a nutshell

npm i
npm run unit-tests
npm audit
node_modules/jshint/bin/jshint src/
npm run jsdoc
open ./docs/jsdoc/index.html
node ./compile.js

To release and deploy to npm

Push a commit with message Release 1.2.3 in master

git commit -m "Release 1.2.3"
git push origin

There's a publication action that will publish released automatically when there's a commit named "Release ..." in master AND the version matches the one in package.json Do not create a git tag for this version, the publication hook will take care of it. If you have created a tag with the release name, the publication will fail

You can follow the results of the actions here

It usually takes a few hours for the package to show up in the NPM UI but you can still use the package by using npm