Created Moving to NPM and Grunt (markdown)

Moving-to-NPM-and-Grunt.md

@@ -0,0 +1,26 @@
+This is a collection of information about, and hopefully decisions for, a move away from pake/build.py to nodejs for the cli development tool chain.
+
+### Related issues and PRs
+
+Plovr-free build (@twpayne) #456
+use-node (@tschaub) #804
+build should use more robust javascript parsing (@twpayne) #308
+Examples and Plovr (@elemoine) #241
+
+### Notes from @twpayne 
+
+   * Plovr provides a single file download that contains a known version the compiler and the compiler library (and more). Without Plovr, we'll have to download these another way.
+   * Plovr allows us to not repeat ourselves with our configurations (all our .json Plovr config files inherit frombase.json).
+   * Plovr is typically faster than running the compiler's calcdeps.py and closurebuilder.py scripts, notably because it avoids JVM start-up in server mode, and that the accessing the Closure library source files packed into the Plovr JAR is much faster than seeking for the files on disk.
+   * Plovr uses the compiler's Java API to invoke the compiler, which allows many more options to be set than can be set via the compiler's command line.
+   * Plovr generally makes using the Closure tools much easier than using the individual scripts.
+   * I think that building the examples with the compiler is an extremely useful validation step and should remain part of the integration tests.
+
+### Replacing Plovr
+
+
+[http://closure-linter.googlecode.com/files/closure_linter-latest.tar.gz](http://closure-linter.googlecode.com/files/closure_linter-latest.tar.gz)
+
+[http://dl.google.com/closure-compiler/compiler-latest.zip](http://dl.google.com/closure-compiler/compiler-latest.zip)
+
+[http://closure-library.googlecode.com/files/closure-library-20130212-95c19e7f0f5f.zip](http://closure-library.googlecode.com/files/closure-library-20130212-95c19e7f0f5f.zip) or `git clone https://code.google.com/p/closure-library/ build/closure-library`