From f7a22d58fdc5116328307a9a6633141346639ec5 Mon Sep 17 00:00:00 2001 From: Paul Spencer Date: Thu, 18 Jul 2013 08:13:22 -0700 Subject: [PATCH] Updated Moving to NPM and Grunt (markdown) --- Moving-to-NPM-and-Grunt.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Moving-to-NPM-and-Grunt.md b/Moving-to-NPM-and-Grunt.md index ae0a581..7140306 100644 --- a/Moving-to-NPM-and-Grunt.md +++ b/Moving-to-NPM-and-Grunt.md @@ -102,6 +102,9 @@ what grunt tasks are required (based on npm script targets) and how we can poten * it would be nice to pick up environment variables that would use existing versions that a developer might install elsewhere and avoid downloading/installing dependencies * how do we make sure the dependencies are updated? Is there an automatic way to do this or is it the responsibility of the developer to periodically do something (clean perhaps?) to trigger an update +* check + * check dependencies, not sure if this needs to be a task or not … + * todo - [https://npmjs.org/package/grunt-todos](https://npmjs.org/package/grunt-todos) * lint - [https://npmjs.org/package/grunt-gjslint](https://npmjs.org/package/grunt-gjslint) which uses [https://github.com/jmendiara/node-closure-linter-wrapper](https://github.com/jmendiara/node-closure-linter-wrapper)