Unleash your code into the wild yonder
npm install unleash--no-publish)--no-push)--list-publishables)
unleash -p -d
`
OR...
`
unleash --patch --dry-run
`
#### Execute a Patch Release
`
unleash -p
`
OR...
`
unleash --patch
`

#### Execute a Major Release
`
unleash -M
`
OR...
`
unleash --major
`#### Execute a Major Package Version Increment w/o Publishing to NPM
`
unleash -M --no-publish
`#### Execute a Major NPM Release w/o Pushing to git
`
unleash -M --no-push
`#### Execute a Minor Release to a Bitbucket Enterprise Repository
`
unleash -m -r bitbucket
`
OR...
`
unleash --minor --repo-type bitbucket
`#### View which files will be published to NPM
This can be helpful in ensuring your package is being published with the least
amount of files possible, while also ensuring you have all the files you need.
We use this to eliminate files like .eslintrc and .tern-project.
`
unleash -ls
`
OR...
`
unleash --list-publishables
`#### Publish your project's documentation to Github Pages
Manually leveraging Github's Pages feature can be tedious. You need to maintain
a branch that's orphaned from master and yet is based on assets and/or tasks
from master. Unleash can help by allowing you to publish files matching a quoted
glob string to gh-pages from the comfort of the branch you normally work on.
`
unleash --gh
defaults to "./docs/*/"
`
OR...
`
unleash --ghpages-deploy --ghpages-path "./public/*/"
`$3
`
perf(pencil): remove graphiteWidth option
fix(graphite): stop graphite breaking when width < 0.1
feat(pencil): add 'graphiteWidth' option
`$3
`
Global w/ latest stable release
npm i unleash -g
`
OR...
`
Locally saved w/ exact version
npm i unleash -DE
`$3
* Major -M | --major
* E.g. "2.6.4" => "3.0.0"
* Minor -m | --minor
* E.g. "2.6.4" => "2.7.0"
* Patch -p | --patch
* E.g. "2.6.4" => "2.6.5"
* Prerelease -P | --prerelease
* E.g. "2.6.4-beta.0" => "2.6.4-beta.1"`