Grails has many tools available but when it comes to front end asset management (compile, concatenate, minify, cache-busting) there are a lot of nice tools coming out of the node.js space,
43. npm http GET https://registry.npmjs.org/bower
npm http 304 https://registry.npmjs.org/bower
npm http GET https://registry.npmjs.org/abbrev
npm http GET https://registry.npmjs.org/async
npm http GET https://registry.npmjs.org/archy
npm http GET https://registry.npmjs.org/colors
npm http GET https://registry.npmjs.org/fstream
npm http GET https://registry.npmjs.org/glob
npm http GET https://registry.npmjs.org/hogan.js
npm http GET https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/lodash
npm http GET https://registry.npmjs.org/nopt
npm http GET https://registry.npmjs.org/promptly
npm http GET https://registry.npmjs.org/rc
npm http GET https://registry.npmjs.org/read-package-json
npm http GET https://registry.npmjs.org/request
npm http GET https://registry.npmjs.org/rimraf
npm http GET https://registry.npmjs.org/stable
npm http GET https://registry.npmjs.org/tar
npm http GET https://registry.npmjs.org/tmp
npm http GET https://registry.npmjs.org/semver
Wednesday, August 7, 13
44. $ npm install bower -g
npm http GET https://registry.npmjs.org/bower
npm http 304 https://registry.npmjs.org/bower
npm http GET https://registry.npmjs.org/abbrev
npm http GET https://registry.npmjs.org/async
npm http GET https://registry.npmjs.org/archy
npm http GET https://registry.npmjs.org/colors
npm http GET https://registry.npmjs.org/fstream
npm http GET https://registry.npmjs.org/glob
npm http GET https://registry.npmjs.org/hogan.js
npm http GET https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/lodash
npm http GET https://registry.npmjs.org/nopt
npm http GET https://registry.npmjs.org/promptly
npm http GET https://registry.npmjs.org/rc
npm http GET https://registry.npmjs.org/read-package-json
npm http GET https://registry.npmjs.org/request
npm http GET https://registry.npmjs.org/rimraf
npm http GET https://registry.npmjs.org/stable
npm http GET https://registry.npmjs.org/tar
npm http GET https://registry.npmjs.org/tmp
npm http GET https://registry.npmjs.org/semver
Wednesday, August 7, 13
73. foo: 1.0.0 exact match
foo: =1.0.0 exact match
foo: >1.0.0 any version GT
foo: <1.0.0 any version LT
foo: >=1.0.0 any version GTE
foo: <=1.0.0 any version LTE
foo: >=1.0.0 < 1.0.9 range
foo: ~1.2.0 range >=1.2.0 <1.3.0
Wednesday, August 7, 13
89. This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sane
defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (my-project)
version: (0.0.0)
description:
entry point: (Gruntfile.js)
test command:
git repository:
keywords:
author:
licence: (BSD)
Wednesday, August 7, 13
90. $ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sane
defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (my-project)
version: (0.0.0)
description:
entry point: (Gruntfile.js)
test command:
git repository:
keywords:
author:
licence: (BSD)
Wednesday, August 7, 13
91. $ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sane
defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (my-project)
version: (0.0.0)
description:
entry point: (Gruntfile.js)
test command:
git repository:
keywords:
author:
licence: (BSD)
Wednesday, August 7, 13
92. $ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sane
defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (my-project)
version: (0.0.0)
description:
entry point: (Gruntfile.js)
test command:
git repository:
keywords:
author:
licence: (BSD)
Wednesday, August 7, 13
93. $ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sane
defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (my-project)
version: (0.0.0) 0.1.0
description:
entry point: (Gruntfile.js)
test command:
git repository:
keywords:
author:
licence: (BSD)
Wednesday, August 7, 13
94. $ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sane
defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (my-project)
version: (0.0.0) 0.1.0
description:
entry point: (Gruntfile.js)
test command:
git repository:
keywords:
author:
licence: (BSD)
Wednesday, August 7, 13
95. $ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sane
defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (my-project)
version: (0.0.0) 0.1.0
description: This is my awesome project
entry point: (Gruntfile.js)
test command:
git repository:
keywords:
author:
licence: (BSD)
Wednesday, August 7, 13
96. $ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sane
defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (my-project)
version: (0.0.0) 0.1.0
description: This is my awesome project
entry point: (Gruntfile.js)
test command:
git repository:
keywords:
author:
licence: (BSD)
Wednesday, August 7, 13
97. $ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sane
defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (my-project)
version: (0.0.0) 0.1.0
description: This is my awesome project
entry point: (Gruntfile.js)
test command:
git repository:
keywords:
author:
licence: (BSD)
Wednesday, August 7, 13
98. $ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sane
defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (my-project)
version: (0.0.0) 0.1.0
description: This is my awesome project
entry point: (Gruntfile.js)
test command: test
git repository:
keywords:
author:
licence: (BSD)
Wednesday, August 7, 13
99. $ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sane
defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (my-project)
version: (0.0.0) 0.1.0
description: This is my awesome project
entry point: (Gruntfile.js)
test command: test
git repository:
keywords:
author:
licence: (BSD)
Wednesday, August 7, 13
100. $ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sane
defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (my-project)
version: (0.0.0) 0.1.0
description: This is my awesome project
entry point: (Gruntfile.js)
test command: test
git repository:http://github.com/zanthrash/my-project
keywords:
author:
licence: (BSD)
Wednesday, August 7, 13
101. $ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sane
defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (my-project)
version: (0.0.0) 0.1.0
description: This is my awesome project
entry point: (Gruntfile.js)
test command: test
git repository:http://github.com/zanthrash/my-project
keywords:
author:
licence: (BSD)
Wednesday, August 7, 13
102. $ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sane
defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (my-project)
version: (0.0.0) 0.1.0
description: This is my awesome project
entry point: (Gruntfile.js)
test command: test
git repository:http://github.com/zanthrash/my-project
keywords: demo
author:
licence: (BSD)
Wednesday, August 7, 13
103. $ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sane
defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (my-project)
version: (0.0.0) 0.1.0
description: This is my awesome project
entry point: (Gruntfile.js)
test command: test
git repository:http://github.com/zanthrash/my-project
keywords: demo
author:
licence: (BSD)
Wednesday, August 7, 13
104. $ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sane
defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (my-project)
version: (0.0.0) 0.1.0
description: This is my awesome project
entry point: (Gruntfile.js)
test command: test
git repository:http://github.com/zanthrash/my-project
keywords: demo
author: Zan Thrash
licence: (BSD)
Wednesday, August 7, 13
105. $ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sane
defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (my-project)
version: (0.0.0) 0.1.0
description: This is my awesome project
entry point: (Gruntfile.js)
test command: test
git repository:http://github.com/zanthrash/my-project
keywords: demo
author: Zan Thrash
licence: (BSD)
Wednesday, August 7, 13
106. Running "init:gruntfile" (init) task
This task will create one or more files in the current directory, based on the
environment and the answers to a few questions. Note that answering "?" to any
question will show question-specific help and answering "none" to most questions
will leave its value blank.
"gruntfile" template notes:
This template tries to guess file and directory paths, but you will most likely
need to edit the generated Gruntfile.js file before running grunt. If you run
grunt after generating the Gruntfile, and it exits with errors, edit the file!
Please answer the following:
[?] Is the DOM involved in ANY way? (Y/n)
[?] Will files be concatenated or minified? (Y/n)
[?] Will you have a package.json file? (Y/n)
[?] Do you need to make any changes to the above before continuing? (y/N)
Wednesday, August 7, 13
107. $ grunt-init gruntfile
Running "init:gruntfile" (init) task
This task will create one or more files in the current directory, based on the
environment and the answers to a few questions. Note that answering "?" to any
question will show question-specific help and answering "none" to most questions
will leave its value blank.
"gruntfile" template notes:
This template tries to guess file and directory paths, but you will most likely
need to edit the generated Gruntfile.js file before running grunt. If you run
grunt after generating the Gruntfile, and it exits with errors, edit the file!
Please answer the following:
[?] Is the DOM involved in ANY way? (Y/n)
[?] Will files be concatenated or minified? (Y/n)
[?] Will you have a package.json file? (Y/n)
[?] Do you need to make any changes to the above before continuing? (y/N)
Wednesday, August 7, 13
108. $ grunt-init gruntfile
Running "init:gruntfile" (init) task
This task will create one or more files in the current directory, based on the
environment and the answers to a few questions. Note that answering "?" to any
question will show question-specific help and answering "none" to most questions
will leave its value blank.
"gruntfile" template notes:
This template tries to guess file and directory paths, but you will most likely
need to edit the generated Gruntfile.js file before running grunt. If you run
grunt after generating the Gruntfile, and it exits with errors, edit the file!
Please answer the following:
[?] Is the DOM involved in ANY way? (Y/n)
[?] Will files be concatenated or minified? (Y/n)
[?] Will you have a package.json file? (Y/n)
[?] Do you need to make any changes to the above before continuing? (y/N)
Wednesday, August 7, 13
109. $ grunt-init gruntfile
Running "init:gruntfile" (init) task
This task will create one or more files in the current directory, based on the
environment and the answers to a few questions. Note that answering "?" to any
question will show question-specific help and answering "none" to most questions
will leave its value blank.
"gruntfile" template notes:
This template tries to guess file and directory paths, but you will most likely
need to edit the generated Gruntfile.js file before running grunt. If you run
grunt after generating the Gruntfile, and it exits with errors, edit the file!
Please answer the following:
[?] Is the DOM involved in ANY way? (Y/n)
[?] Will files be concatenated or minified? (Y/n)
[?] Will you have a package.json file? (Y/n)
[?] Do you need to make any changes to the above before continuing? (y/N)
Wednesday, August 7, 13
110. $ grunt-init gruntfile
Running "init:gruntfile" (init) task
This task will create one or more files in the current directory, based on the
environment and the answers to a few questions. Note that answering "?" to any
question will show question-specific help and answering "none" to most questions
will leave its value blank.
"gruntfile" template notes:
This template tries to guess file and directory paths, but you will most likely
need to edit the generated Gruntfile.js file before running grunt. If you run
grunt after generating the Gruntfile, and it exits with errors, edit the file!
Please answer the following:
[?] Is the DOM involved in ANY way? (Y/n)
[?] Will files be concatenated or minified? (Y/n)
[?] Will you have a package.json file? (Y/n)
[?] Do you need to make any changes to the above before continuing? (y/N)
Wednesday, August 7, 13
111. $ grunt-init gruntfile
Running "init:gruntfile" (init) task
This task will create one or more files in the current directory, based on the
environment and the answers to a few questions. Note that answering "?" to any
question will show question-specific help and answering "none" to most questions
will leave its value blank.
"gruntfile" template notes:
This template tries to guess file and directory paths, but you will most likely
need to edit the generated Gruntfile.js file before running grunt. If you run
grunt after generating the Gruntfile, and it exits with errors, edit the file!
Please answer the following:
[?] Is the DOM involved in ANY way? (Y/n)
[?] Will files be concatenated or minified? (Y/n)
[?] Will you have a package.json file? (Y/n)
[?] Do you need to make any changes to the above before continuing? (y/N)
n
Wednesday, August 7, 13
112. $ grunt-init gruntfile
Running "init:gruntfile" (init) task
This task will create one or more files in the current directory, based on the
environment and the answers to a few questions. Note that answering "?" to any
question will show question-specific help and answering "none" to most questions
will leave its value blank.
"gruntfile" template notes:
This template tries to guess file and directory paths, but you will most likely
need to edit the generated Gruntfile.js file before running grunt. If you run
grunt after generating the Gruntfile, and it exits with errors, edit the file!
Please answer the following:
[?] Is the DOM involved in ANY way? (Y/n)
[?] Will files be concatenated or minified? (Y/n)
[?] Will you have a package.json file? (Y/n)
[?] Do you need to make any changes to the above before continuing? (y/N)
n
Wednesday, August 7, 13
161. $ npm install zanthrash/generator-grails-angular
Wednesday, August 7, 13
162. Would you like to include Twitter Bootstrap? (Y/n)
If so, would you like to use Twitter Bootstrap for Sass (as opposed to vanilla
CSS)? (Y/n)
Would you like to use CoffeeScript (Y/n)
Would you like to include angular-resource.js? (Y/n)
Would you like to include angular-cookies.js? (Y/n)
Would you like to include angular-sanitize.js? (Y/n)
Wednesday, August 7, 13
163. $ yo grails-angular
Would you like to include Twitter Bootstrap? (Y/n)
If so, would you like to use Twitter Bootstrap for Sass (as opposed to vanilla
CSS)? (Y/n)
Would you like to use CoffeeScript (Y/n)
Would you like to include angular-resource.js? (Y/n)
Would you like to include angular-cookies.js? (Y/n)
Would you like to include angular-sanitize.js? (Y/n)
Wednesday, August 7, 13
164. $ yo grails-angular
Would you like to include Twitter Bootstrap? (Y/n)
If so, would you like to use Twitter Bootstrap for Sass (as opposed to vanilla
CSS)? (Y/n)
Would you like to use CoffeeScript (Y/n)
Would you like to include angular-resource.js? (Y/n)
Would you like to include angular-cookies.js? (Y/n)
Would you like to include angular-sanitize.js? (Y/n)
Wednesday, August 7, 13
165. $ yo grails-angular
Would you like to include Twitter Bootstrap? (Y/n)
If so, would you like to use Twitter Bootstrap for Sass (as opposed to vanilla
CSS)? (Y/n)
Would you like to use CoffeeScript (Y/n)
Would you like to include angular-resource.js? (Y/n)
Would you like to include angular-cookies.js? (Y/n)
Would you like to include angular-sanitize.js? (Y/n)
Wednesday, August 7, 13
166. $ yo grails-angular
Would you like to include Twitter Bootstrap? (Y/n)
If so, would you like to use Twitter Bootstrap for Sass (as opposed to vanilla
CSS)? (Y/n)
Would you like to use CoffeeScript (Y/n)
Would you like to include angular-resource.js? (Y/n)
Would you like to include angular-cookies.js? (Y/n)
Would you like to include angular-sanitize.js? (Y/n)
Wednesday, August 7, 13
167. $ yo grails-angular
Would you like to include Twitter Bootstrap? (Y/n)
If so, would you like to use Twitter Bootstrap for Sass (as opposed to vanilla
CSS)? (Y/n)
Would you like to use CoffeeScript (Y/n)
Would you like to include angular-resource.js? (Y/n)
Would you like to include angular-cookies.js? (Y/n)
Would you like to include angular-sanitize.js? (Y/n)
Wednesday, August 7, 13
168. $ yo grails-angular
Would you like to include Twitter Bootstrap? (Y/n)
If so, would you like to use Twitter Bootstrap for Sass (as opposed to vanilla
CSS)? (Y/n)
Would you like to use CoffeeScript (Y/n)
Would you like to include angular-resource.js? (Y/n)
Would you like to include angular-cookies.js? (Y/n)
Would you like to include angular-sanitize.js? (Y/n)
Wednesday, August 7, 13
169. $ yo grails-angular
Would you like to include Twitter Bootstrap? (Y/n)
If so, would you like to use Twitter Bootstrap for Sass (as opposed to vanilla
CSS)? (Y/n)
Would you like to use CoffeeScript (Y/n)
Would you like to include angular-resource.js? (Y/n)
Would you like to include angular-cookies.js? (Y/n)
Would you like to include angular-sanitize.js? (Y/n)
Wednesday, August 7, 13