ashatora/openlayers
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Updated Moving to NPM and Grunt (markdown)

Paul Spencer
2013-07-18 08:02:16 -07:00
parent cc717c33b5
commit 86550bfd7c
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Moving-to-NPM-and-Grunt.md
+4
@@ -95,9 +95,13 @@ what grunt tasks are required (based on npm script targets) and how we can poten
* [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`
* 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
* 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)
* may want to investigate how this works, the wrapper claims to embed a specific version with local modifications. In my mind, we should avoid embedded versions if possible.
* build - [https://npmjs.org/package/grunt-closure-compiler](https://npmjs.org/package/grunt-closure-compiler)