webapp-annotated-build-scaffolding | Grunt scaffolding to build LESS | Style Language library

Download this project however you think is feasible. Either download ZIP or. The choice is yours. Remember to change infomation in package.json and bower.json to yours. You probably don’t want to remove any dependencies from package.json unless you really know what you are doing. But feel free to change all the dependencies in bower.json, which serves purely as example. If this is your first time playing with this scaffolding, please take a look at src directory as a sample, otherwise, delete everything under src directory and setup your project with your liking. (May I suggest [HTML5 Boilerplate](http://html5boilerplate.com/)?). Annotate JavaScript and CSS tags in your HTML files with [htmlrefs](https://github.com/tactivos/grunt-htmlrefs) and [usemin](https://github.com/yeoman/grunt-usemin) blocks. Open Gruntfile.js and edit copy:assets, copy:dev, copy:qa, copy:prd targets to your liking. (Feel free to add more build tasks. Scroll to the bottom of Gruntfile.js to see how current build tasks are registered. It should be pretty straightforward.). Now you can build your project with: grunt dev, grunt qa and grunt prd. Here are the differences between these tasks. Due to the fact that [CommonJS](http://wiki.commonjs.org/wiki/CommonJS) moduels need to be wrapped by [Browserify](http://browserify.org/) before running in a browser, there are tasks to make it more convenient. Additionally, there’s a watch:dev task to watch for changes to config files and run dev task. This task could come in handy when you are actively editing your config files, otherwise it’s pretty useless. Of course, there’s clean task to clean everything generated by [Grunt](http://gruntjs.com/).
dev is very straightforward. It simply copies development configs to your src directory. You are expected to develop from your src directory with everything in their raw form.
qa copies QA configs to src as well as dist direcotry. It then compiles, minifies and generates JavaScript, CSS and HTML with JavaScript source maps. Everything inside dist directory is ready for distribution. (You should be able to just ZIP up dist directory and send it to QA.)
prd copies production configs to src as well as dist direcotry. It is very similar to QA build, except it doesn’t generate JavaScript source map. Again, dist directory is ready for distribution.
devCommonJs builds [CommonJS](http://wiki.commonjs.org/wiki/CommonJS) modules with minimun amount of process. It does not perform any kind of minification or even full clean to keep things running as fast as possible. But you will have to run your app from dist directory instead.
watch:devCommonJs uses [grunt-contrib-watch](https://github.com/gruntjs/grunt-contrib-watch) to watch changes you make. It will automatically run devCommonJs task whenever you save files. You should take a quick look at the watch task configs in Gruntfile.js to make sure that it ignored all the files you modify during build to avoid infinite build calls.