HBS UIKIT

Builds general ui- and form elements in hbs design

Start Demo Mode locally

$ npm start

or

$ yarn start

Build locally

$ npm run build

Release to production.

$ npm version [major | minor | patch | ... ]

This will increase the package version number in package.json, refresh the dist files and tags the resulting state with a commit tag. For more arguments see npm version.

E.g.:

$ npm version patch
$ git push && git push --tags

Publish a local state to npm registry.

Generate a valid version string with a string tag of your choice.

npm run --silent getSuccessorVersion <yourChoice>
> 0.1.11-<yourChoice>.0

The returned string e.g.: 0.1.11-<yourChoice>.0 is a valid never published version string. Now you can update and publish your package with the returned version string:

npm version 0.1.11-<yourChoice>.0
npm publish --tag=dev

Afterwards the package can be referenced by the version string 0.1.11-<yourChoice>.0 in your consuming node package.

Release feature branch to branch.

For release of your branch. Just push your git branch to the remote repository. If your branch <branch> has the version 1.2.3, the resulting package version will be 1.2.4-<branch>.0. Which can be referenced in your consumer package like:

...
"dependencies": {
    ...
    "@pinuts/hbs-uikit": "1.2.4-<branch>.0",
    ...
},
...

Pay Attention the patch part of the version is increased by one.

(see also puppetmaster