gulp-bower-normalize

Use rules in the bower.json or implicit rules to normalize the files being copied out of bower_components so that a consistent and clean version of the bower dependencies can be checked into the repo. This is intended to work with main-bower-files.

INSTALL

npm install --save-dev gulp-bower-normalize

USAGE

Designed to work with main-bower-files as so:

1gulp.task('default', function() {
2    var bower = require('main-bower-files');
3    var bowerNormalizer = require('gulp-bower-normalize');
4    return gulp.src(bower(), {base: './bower_components'})
5        .pipe(bowerNormalizer({bowerJson: './bower.json'}))
6        .pipe(gulp.dest('./bower_dependencies/'))
7});

bower.json

1{
2    name and otherstuff
3    "dependencies": {
4        "dependency1": "~1.0.1"
5        "dependency2": "~1.0.1"
6        "dependency3": "~1.0.1"
7        "dependency4": "~1.0.1"
8    },
9    "overrides": {
10        // Muli allows one normalize definition to span multiple dependencies
11        // NOTE: This is first one in wins for the multi list and will always
12        // defer to the overrides.
13        "normalizeMulti": [
14            {
15                "dependencies": ["dependency1", "dependency2"],
16                "normalize": {
17                    "img": ["*.jpeg", "*.png", "*.jpg"],
18                    "font": ["*.ttf", "*.woff2"]
19                }
20            },
21            {
22                "dependencies": ["dependency2", "dependency3"],
23                "normalize": {
24                    // Note since dependency3 defines js, it won't get this definition
25                    "js": ["*.js", "*.less"],
26                }
27            },
28            {
29                "dependencies": ["dependency2"],
30                "normalize": {
31                    // Note since dependency2 already had js defined by the multi, it won't get this definition
32                    "js": ["*.*"],
33                }
34            }
35        ],
36        // Implicitly normalizes this file by file extension 'dependency1/js/some.js'
37        "dependency1": {
38            "main": "some.js"
39        },
40        // Implicitly organized into 'dependency2/js/some.js' 'dependency2/js/some.js'
41        "dependency2": {
42            "main": ["some.js", "some.css"]
43        },
44        // Explicitly organized into 'dependency3/js/some.js', 'dependency3/css/some.ext', 'dependency3/css/some.css'
45        "dependency3": {
46            "main": ["some.js", "some.ext", "some.css"],
47            "normalize": {
48                "js": "*.js",
49                "css": ["*.ext", "*.css"]
50            }
51        } // dependency4 is implicitly organized into 'dependency4/<ext>/<file>
52    }
53}

Note: Comments are not valid JSON, so if you're copying this, you'll need to remove them.

API

bowerNormalize(options)

options.basePath

Type: string Default: process.cwd()

Path to search for the bower.json file in.

options.bowerJson

Type: string Default: ./bower.json

Path to bower.json that overrides will come from. This should be relative to options.BasePath.

options.flatten

Type: boolean Default: false

Option to remove the component level folders. This would turn /lib/jquery/js/jquery.js into /lib/js/jquery.js.

Note: If your components have files with the same name then only one of them will be included in the results.

options.typeTop

Type: boolean Default: false

Option to put the type folder on top of the hierarchy. This would turn /lib/jquery/js/jquery.js into /lib/js/jquery/jquery.js.

options.checkPath

Type: boolean Default: false

This option allows a multi-level path on the normalization destination. This allows matching similar to the following:

 "dependency7": {
      "main": ["some.js", "some/other.js"],
      "normalize": {
        "js": "*.js",
        "js/some": "**/some/*.js"
      }
 }

Note: This will not work in conjunction with the flatten option.

Frequently Asked Questions

Unexpected folder normalization

Be aware of your JSON keys of the normalize property of your bower.json.
Only unique JSON keys could be parsed correctly into your expected destination folder structure.

Example

This could lead to unexpected normalization

"normalize": {
  ".": "**/*.scss",
  ".": "**/*.js"
}

The right expression should be

"normalize": {
  ".": ["**/*.scss", "**/*.js"]
}

License

MIT © Myles Bostwick