concept release in category javascript

This is an excerpt from Manning's book JavaScript Application Design: A Build First Approach.
Deployed code that’s always tested before a release
Listing 3.1. Distributed build configuration
grunt.initConfig({ jshint: { client: ['public/js/**/*.js'], server: ['server/**/*.js'], support: ['Gruntfile.js'] }, less: { debug: { #1 files: { 'build/css/layout.css': 'public/css/layout.less', #2 'build/css/home.css': 'public/css/home.less' } }, release: { #3 files: { 'build/css/all.css': [ 'public/css/**/*.less' #4 ] } } }, jade: { debug: { options: { #5 pretty: true }, files: { 'build/views/home.html': 'public/views/home.jade' } }, release: { files: { 'build/views/home.html': 'public/views/home.jade' } } } }); #1: The less:debug task target compiles LESS files into CSS for development purposes. #2: The file found at the path in the value will be compiled into the path in the property. #3: The release target is only used during the release build flow. #4: A globbing pattern compiles all LESS style sheets into a single output CSS file. #5: Note how jade:debug sets options different from those in release flows.
We’ve covered the build process, common build tasks you can perform (and how to do that using Grunt), and, at a high level, environments and configuration. We discussed the development environment extensively, but that’s only half the story. The development environment is where you’ll spend most of your time working, because you’ll have a system in place, so you can prepare your application for a release, deploy it to a platform that humans can access, and then monitor the application state. Thanks to the Build First mentality, you’ll be automating the workflows I’ve just mentioned, avoiding repetition, human error, and running tests, all while saving time, as I promised in chapter 1.