A grunt task to ensure you are using the node version required by your project's package.json
This plugin requires Grunt
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-node-version --save-dev
In your project's Gruntfile, add a section named
node_version to the data object passed into
Prepend any task lists that contain grunt-exec tasks with the
node_version task, and it will extend
grunt-exec tasks by prepending them with an
nvm use command when necessary.
A boolean that determines whether to install the latest compatible version of node without a prompt (default behavior prompts user to install). This is primarily intended to be used for deployment.
The level of error given when the wrong node version is being used. Accepted values are
'fatal'. Warn can can be overidden with
--force, fatal cannot.
An array of node modules required to be installed globally for the project.
Specifies the largest amount of data allowed on stdout or stderr - if this value is exceeded then the child process is killed. If using older versions of node or NVM, you may need to increase this number for successful installation.
A boolean that determines whether to attempt to use/install a version of node compatible with the project using NVM. If set to
false, the plugin will just print an error if the wrong node version is being used.
If you want to override the version specified in your project's
package.json, specify the version you want to use instead here. This is primarily intended for testing projects on other versions of node.
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.