Helps you keep your code less crazy by adding either eslint or jshint in the pre-commit hooks.
In your project root directory, type:
$ npm install --save-dev abracadabra
and that's it.
Upon installation it adds a git pre-commit hook in your repository, which runs every time you're going to commit something. In this case it'll run a npm task that validates your code either via eslint
or jshint
. In that way, anybody in your team can't commit anything that doesn't match the standards.
It's up to you. If you don't have any eslint
or jshint
configurations in your root directory, it'll ask you and then create a default configuration for linter of your choice. You may later change configurations according to your needs.
How it is different from this?
There are two major differences, one being that nlf/precommit-hook
only supports jshint
and has it in its dependencies, while abracadabra
supports jshint
as well as eslint
moreover it uses the lint command from your dependencies. Plus, it has quite verbose default configuration files. Other than that, it uses the same nlf/git-validate
module under the hood as precommit-hook
.
Here they are; .eslintrc
& .jshintrc
.
You can bypass the pre-commit hook by:
$ git commit --no-verify
See Issue: #1. In short, start you GUI app from terminal.