Bumps [husky](https://github.com/typicode/husky) from 1.1.4 to 1.2.0.
- [Release notes](https://github.com/typicode/husky/releases)
- [Changelog](https://github.com/typicode/husky/blob/master/CHANGELOG.md)
- [Commits](typicode/husky@v1.1.4...v1.2.0)

Signed-off-by: dependabot[bot] <support@dependabot.com>

Changed the `colors` based codebase to a `chalk` one with some colour changes (out -> cyan without
bold, warn -> orange); added a `getTheme` function while removing the `theme` script

BREAKING CHANGE: No longer accept `colors` specific styles in `extend()` (e.g: "grey", "rainbow",
"zebra", "america", "trap" and "random") but accept more choices. Some colours could be slightly
different (so that could break tests relying on those).

fix #2

Updated the documentation and re-added `bold` to `info()` (so this is no longer a **breaking**
change for `info()` _only_)

Testing if `chalk` is enabled on TravisCI or if the fail is caused by something else (while working
locally).

Updated the pre-commit hook according to the new way of doing it.

Reset the _package.json_  and the package lock

Attempt at fixing [this issue](https://github.com/chalk/chalk/issues/307) with what @nazrhyn
suggested.

re #2

Changed `npm test` to run `jest --color` instead of `jest --color=always`, removed the
`chalk.colour` forcer in _index.js_ and tweaked a test case.

re #2

Refactored duplicated block of lines flagged in Codacy

Made the `chalk` colour forcing unconditional and as complex as it needs to be (for now).

Refactored a new set of duplicated block (3 lines).

Removed the duplicated variable declaration that stayed after a merge conflict.

…sky-1.2.0

Bumps [semantic-release](https://github.com/semantic-release/semantic-release) from 15.12.3 to 15.12.4.
- [Release notes](https://github.com/semantic-release/semantic-release/releases)
- [Commits](semantic-release/semantic-release@v15.12.3...v15.12.4)

Signed-off-by: dependabot[bot] <support@dependabot.com>

…mantic-release-15.12.4

Changed the `colors` based codebase to a `chalk` one with some colour changes (out -> cyan without
bold, warn -> orange); added a `getTheme` function while removing the `theme` script

BREAKING CHANGE: No longer accept `colors` specific styles in `extend()` (e.g: "grey", "rainbow",
"zebra", "america", "trap" and "random") but accept more choices. Some colours could be slightly
different (so that could break tests relying on those).

fix #2

Updated the documentation and re-added `bold` to `info()` (so this is no longer a **breaking**
change for `info()` _only_)

Testing if `chalk` is enabled on TravisCI or if the fail is caused by something else (while working
locally).

Updated the pre-commit hook according to the new way of doing it.

Reset the _package.json_  and the package lock

Attempt at fixing [this issue](https://github.com/chalk/chalk/issues/307) with what @nazrhyn
suggested.

re #2

Changed `npm test` to run `jest --color` instead of `jest --color=always`, removed the
`chalk.colour` forcer in _index.js_ and tweaked a test case.

re #2

Refactored duplicated block of lines flagged in Codacy

Made the `chalk` colour forcing unconditional and as complex as it needs to be (for now).

Refactored a new set of duplicated block (3 lines).

Removed the duplicated variable declaration that stayed after a merge conflict.

Bumps [colors](https://github.com/Marak/colors.js) from 1.3.2 to 1.3.3.
- [Release notes](https://github.com/Marak/colors.js/releases)
- [Commits](Marak/colors.js@v1.3.2...v1.3.3)

Signed-off-by: dependabot[bot] <support@dependabot.com>

…lors-1.3.3

Bumps [documentation](https://github.com/documentationjs/documentation) from 8.1.2 to 9.0.0.
- [Release notes](https://github.com/documentationjs/documentation/releases)
- [Changelog](https://github.com/documentationjs/documentation/blob/master/CHANGELOG.md)
- [Commits](documentationjs/documentation@v8.1.2...v9.0.0)

Signed-off-by: dependabot[bot] <support@dependabot.com>

…cumentation-9.0.0

Bumps [eslint](https://github.com/eslint/eslint) from 5.9.0 to 5.10.0.
- [Release notes](https://github.com/eslint/eslint/releases)
- [Changelog](https://github.com/eslint/eslint/blob/master/CHANGELOG.md)
- [Commits](eslint/eslint@v5.9.0...v5.10.0)

Signed-off-by: dependabot[bot] <support@dependabot.com>

…lint-5.10.0

Switched to the non-deprecated pre-commit hook approach recommended when using `husky`

Added a log for successes called `succ`.

… chalk-based

Added logs for successes (`succ`) which uses the previous colour of `info` which now uses bright
blue.

Changed the `colors` based codebase to a `chalk` one with some colour changes (out -> cyan without
bold, warn -> orange); added a `getTheme` function while removing the `theme` script

BREAKING CHANGE: No longer accept `colors` specific styles in `extend()` (e.g: "grey", "rainbow",
"zebra", "america", "trap" and "random") but accept more choices. Some colours could be slightly
different (so that could break tests relying on those).

fix #2

Updated the documentation and re-added `bold` to `info()` (so this is no longer a **breaking**
change for `info()` _only_)

Testing if `chalk` is enabled on TravisCI or if the fail is caused by something else (while working
locally).

Updated the pre-commit hook according to the new way of doing it.

Reset the _package.json_  and the package lock

Attempt at fixing [this issue](https://github.com/chalk/chalk/issues/307) with what @nazrhyn
suggested.

re #2

Changed `npm test` to run `jest --color` instead of `jest --color=always`, removed the
`chalk.colour` forcer in _index.js_ and tweaked a test case.

re #2

Refactored duplicated block of lines flagged in Codacy

Made the `chalk` colour forcing unconditional and as complex as it needs to be (for now).

Refactored a new set of duplicated block (3 lines).

Removed the duplicated variable declaration that stayed after a merge conflict.

Changed the `colors` based codebase to a `chalk` one with some colour changes (out -> cyan without
bold, warn -> orange); added a `getTheme` function while removing the `theme` script

BREAKING CHANGE: No longer accept `colors` specific styles in `extend()` (e.g: "grey", "rainbow",
"zebra", "america", "trap" and "random") but accept more choices. Some colours could be slightly
different (so that could break tests relying on those).

fix #2

Updated the documentation and re-added `bold` to `info()` (so this is no longer a **breaking**
change for `info()` _only_)

Testing if `chalk` is enabled on TravisCI or if the fail is caused by something else (while working
locally).

Reset the _package.json_  and the package lock

Changed `npm test` to run `jest --color` instead of `jest --color=always`, removed the
`chalk.colour` forcer in _index.js_ and tweaked a test case.

re #2

Made the `chalk` colour forcing unconditional and as complex as it needs to be (for now).

Removed the duplicated variable declaration that stayed after a merge conflict.

Added logs for successes (`succ`) which uses the previous colour of `info` which now uses bright
blue.

Re-applied pre-rebase changes.

And fixed the package lock.

…ased

Refactored most test cases and fixed the 3 that were broken.

Added symbolic versions accessible using `./symbols` which only changes `info`, `error`, `warn`,
`quest` and `succ`. `./index` was also refactored to take advantage of the common code with
`./symbols` while making sure the theme was just as accessible within the package.

`extend()` now properly rejects undefined values which in the past let functions (cf.
`harmless(...)` in the test suites) pass as "undefined".

As suggested by @cotsog on the TravisCI ticket, this should allow the terminal to use enough
colours.

re chalk/supports-color#92

Try with --color=16m