My first naïve attempt, was just running the grunt.js file as found in the project directory. This failed with the following message:
Going back to the project site, I found that you have to use Grunt(a node.js plugin) for building:
The library uses grunt for building. Alternatively, you can download the latest build from here.Ok, let’s try this. I opened a command window and tried to execute the command(notice that I already have node.js installed on my machine):
Run the full build process (including lint, qunit and webdriver tests):
npm install -g grunt-cli
This will put the
gruntcommand in your system path, allowing it to be run from any directory.
Let’s now run the grunt command(you can use both grunt and grunt.cmd):
Woops. No success. I figured out that I was using a more recent version of Grunt than the project was using. In the meanwhile the convention had changed and instead of having a grunt.js file in your project directory, you need to name it gruntfile.js(More info here: http://gruntjs.com/getting-started).
TheRun the command again, still failure:
package.jsonfile, and should be committed with your project source.
A Gruntfile is comprised of the following parts:
· The "wrapper" function
· Project and task configuration
· Loading grunt plugins and tasks
· Custom tasks
Grunt itself is doing nothing, it only loads a set of plugins and tasks and execute them. It seems that grunt tried to execute some tasks that I didn’t install. So let’s install the missing packages and try again:
Ok, last attempt, this time we finally got Grunt working:
And now I have a nice new tool in my toolbox.