Share frontend assets between different web repositories
The workflow for development will be usually this:
grunt devin one tab to see the styleguide html view working, which is open by default.
grunt testin another tab to run the tests. This uses karma underneath.
For more details, take a look to the
Grunfile to see all tasks available.
In order to release a new version of Hangar, from master branch run:
npm run release
This will make a new build, publish the new version to github pages and then launch the interactive UI that guides you through publishing a new version to npm and unpkg:
As we already published hangar to npm, unpkg.com is the best choice, and the good thing is, we don't need to do anything to version the assets:
Use @latest as latest version.