Helps keep code to defined standards
This plugin requires Grunt ~0.4.1
If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
npm install grunt-criterion --save-dev
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks('grunt-criterion');Takes .js files inside of the working directory and runs one or more of the following tasks
grunt (jshint)
Outputs a list of errors to log.json. By default, ignores the following errors:
Mixed spaces and tabs -- W099
grunt b
Once jshint passes to satisfaction, it's recommended to run this to neatly format the code. Note this takes care of the defaulted second error, aforementioned.
grunt c
This adds a custom comment to the beginning of your js file, should you choose. (WORK IN PROGRESS)
If you're so inclined, this package takes advantage of an express webserver and code mirror. Running
node web.js
Fires a webserver on port 7000 that keeps track of the present errors inside log.json. Simply navigate to
localhost:7000
to view any errors. You can modify and save the errors right in the browser!
To make that editor above even easier to use, you can run
grunt watch
on your directory. Every saved watch file will be jshinted, and all errors will automatically show up in the localhost editor.
You want coverage tests of your code? Write your own mocha tests, and run
grunt mocha
Your coverage test will be outputted to /coverage
If you're so inclined, you can run coverage tests on each js file in your directory. Run
grunt cover
Your coverage test will be outputted to /coverage.
If you'd like to document your code using jsduck format, just simply run
grunt duck
You'll be prompted for input directories (comma delimited list, no spaces), and docs will output to /docs