From ba6d513f67ccb1a7033115facd2557809657c638 Mon Sep 17 00:00:00 2001 From: Paul Spencer Date: Tue, 23 Jul 2013 05:37:56 -0700 Subject: [PATCH] Updated Moving to NPM and Grunt (markdown) --- Moving-to-NPM-and-Grunt.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Moving-to-NPM-and-Grunt.md b/Moving-to-NPM-and-Grunt.md index 14c2009..92624ec 100644 --- a/Moving-to-NPM-and-Grunt.md +++ b/Moving-to-NPM-and-Grunt.md @@ -138,6 +138,10 @@ what grunt tasks are required (based on npm script targets) and how we can poten * 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 * perhaps install always updates the dependencies to the current version (if not overridden by env variables) and the check task only installs if missing? + * (@probins) it may be possible to avoid a local java install for casual use if we used Google's web service - see https://github.com/weaver/scribbles/tree/master/node/google-closure/ + + * (@twpayne) glsl-unit latest npm package does not work, use https://code.google.com/p/glsl-unit/ instead + * check - custom code * check for the existence of a dependency * other tasks use this to ensure dependencies are available