krimzen-ninja-common-errors

 [](https://codecov.io/gh/KrimZen Ninja/krimzen-ninja-common-errors)

A collection of custom common errors that can be used across projects and modules.

Install

$ npm install --save krimzen-ninja-common-errors

Usage

import myModule from 'krimzen-ninja-common-errors'

myModule()
//TODO

API

[See details](https://github.com/KrimZen Ninja/krimzen-ninja-common-errors/blob/master/API.md)

License

MIT © [Ryan Kotzen](https://github.com/KrimZen Ninja)

Contributing to this module

Install Chandler to sync your CHANGELOG.md entries to GitHub

How to publish to NPM

You can either do releases from the master branch or follow the LTS model and branch off when you do a release.

1. Ensure you are on the branch you want to publish from.
2. Decide based on what is going into the release how the version number is going to change, see Semantic Versioning for more info.
3. The CHANGELOG.md file should have pending changes documented in the Unreleased section, create a new heading for this version and cut the relevant changes and paste them into the new section.
4. Commit the changes to the CHANGELOG.md file.
5. Run one of the prebuilt publish commands that matches your semver patch, minor, major

   npm run patch -m "A message that makes sense" If none of the prebuilt ones fit, you can use npm version [major | minor | patch | premajor | preminor | prepatch | prerelease] -m "A message that makes sense"

6. If you didn't publish from master, make sure to merge back into master if you were fixing a bug or the changes released need to go back to master.

Snyk dependency checking

You can either add your project via the web dashboard or via the cli by installing the lib npm i -g snyk and then running the setup snyk wizzard.