		/jslint node: true /
		'use strict';

		var pkg = require('./package.json');

		//Using exclusion patterns slows down Grunt significantly
		@@ -83,3 +85,3 @@ //instead of creating a set of patterns like '*/.js' and '!/node_modules/'
		options: {
		module:'<%= _.slugify(appname) %>',
		module: pkg.name,
		htmlmin:'<%%= htmlmin.main.options %>'
		@@ -156,3 +158,2 @@ },
		removeEmptyAttributes: true,
		removeRedundantAttributes: true,
		removeScriptTypeAttributes: true,
		@@ -159,0 +160,0 @@ removeStyleLinkTypeAttributes: true

directive/index.js

		@@ -70,4 +70,4 @@ 'use strict';

		cgUtils.processTemplates(this.name,this.dir,'service',this,defaultDir,configName);
		cgUtils.processTemplates(this.name,this.dir,'directive',this,defaultDir,configName);

		};

package.json

		{
		"name": "generator-cg-angular",
		"version": "3.0.0",
		"version": "3.0.2",
		"description": "Yeoman Generator for Enterprise Angular projects.",
		@@ -5,0 +5,0 @@ "keywords": [

README.md

		@@ -135,6 +135,7 @@ #generator-cg-angular

		Importantly, `grunt-dom-munger` uses JQuery selectors to manage the parsing of the script tags. It is very easy to exclude certain scripts from the build. For example, the project includes a references to the `livereload.js` from the `grunt-contrib-watch` task. But this file should not be included in a production build. Thus the `grunt-dom-munger` task is configured with a selector like `script[data-build!="exclude"]` and the script tag for `livereload.js` includes an attribute like `data-build="exclude"`. You can use this flexibility in your project to include/exclude scripts in your production builds.
		Importantly, `grunt-dom-munger` uses CSS selectors to manage the parsing of the script tags. It is very easy to exclude certain scripts from the build. For example, the project includes a references to the `livereload.js` from the `grunt-contrib-watch` task. But this file should not be included in a production build. Thus the `grunt-dom-munger` task is configured with a selector like `script[data-build!="exclude"]` and the script tag for `livereload.js` includes an attribute like `data-build="exclude"`. You can use this flexibility in your project to include/exclude scripts in your production builds.

		Release History
		-------------
		* 3/10/2014 - v3.0.2 - Fix for directive files not being named correctly. Fix for htmlmin from affecting some Bootstrap styles.
		* 3/03/2014 - v3.0.0 - All sub-generators now ask the user for a directory enabling any user-defined project structure. Gruntfile has been altered to allow scripts, partials, and LESS files to be located anywhere in the project directory structure. An option to use `angular-ui-router` is now available when initializing a new project. `js/setup.js` and `css/app.less` moved to `app.js` and `app.less`. `grunt server` is now `grunt serve`. Inside `index.html` all user script tags are grouped together instead of split out into groups for services/filters/etc. New ability to customize the sub-generators.
		@@ -141,0 +142,0 @@ * 2/10/2014 - v2.1.1 - Fix for the directive spec file named with a .less extension.

generator-cg-angular - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics