Gathering detailed insights and metrics for gulp-bower-files
Gathering detailed insights and metrics for gulp-bower-files
Gathering detailed insights and metrics for gulp-bower-files
Gathering detailed insights and metrics for gulp-bower-files
gulp-main-bower-files
Use main-bower-files in a more gulp like way.
gulp-bower-normalize
Takes a list of bower files and normalizes them by as <package name>/<type> where type is inferred by file extension or taken from 'override' section of bower.json
gulp-bower-files-from-html
Extract the bower files from the html files according to script and link tags.
gulp-bower-src
gulp-src bower files
npm install gulp-bower-files
Typescript
Module System
NPM Version
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
80 Stars
78 Commits
13 Forks
1 Watchers
2 Branches
9 Contributors
Updated on Mar 03, 2022
Latest Version
0.2.7
Package Id
gulp-bower-files@0.2.7
Size
7.24 kB
NPM Version
1.4.3
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
1
4
Package | gulp-bower-files |
Description | Build gulp.src() of your bower package's main files. |
Node Version | >= 0.10 |
1var gulpBowerFiles = require('gulp-bower-files'); 2 3gulp.task("bower-files", function(){ 4 gulpBowerFiles().pipe(gulp.dest("./lib")); 5});
This will read your bower.json
, iterate through your dependencies and build a gulp.src()
with all files defined in the main property of the packages bower.json
.
You can override the behavior if you add an overrides
property to your own bower.json
. E.g.:
These options can be set directly in your bower.json
file, e.g.:
1{ 2 "name": "your-package-name", 3 "dependencies": { 4 "BOWER-PACKAGE": "*" 5 }, 6 "overrides": { 7 "BOWER-PACKAGE": { 8 // Here you can override the main files or ignoring this package, for more info see options 9 } 10 } 11}
Type: String
or Array
or Object
You can specify which files should be selected. You can gulp-bower-files
select files based on the process.env.NODE_ENV
if you provide an Object
with keys
as the environment, e.g.:
1{ 2 "overrides": { 3 "BOWER-PACKAGE": { 4 "main": { 5 "development": "file.js", 6 "production": "file.min.js", 7 } 8 } 9 } 10}
Type: Boolean
Default: false
Set to true
if you want to ignore this package.
Type: Object
You can override the dependencies of a package. Set to null
to ignore the dependencies.
These options can be passed to this plugin, e.g: bowerFiles(/* options*/)
Type: boolean
Default: false
Set to true
to enable debugging output.
Type: String
or Array
or Object
Default: null
You can specify for all packages a default main property which will be used if the package does not provide a main property.
Type: String
Default: process.env.NODE_ENV
If process.env.NODE_ENV
is not set you can use this option.
Type: Object
or String
You can specify the paths where the following bower specific files are located:
bower_components
, .bowerrc
and bower.json
For example:
1bowerFiles({ 2 paths: { 3 bowerDirectory: 'path/for/bower_components', 4 bowerrc: 'path/for/.bowerrc', 5 bowerJson: 'path/for/bower.json' 6 } 7}) 8.pipe(gulp.dest('client/src/lib'));
If a String
is supplied instead, it will become the basepath for default paths.
For example:
1bowerFiles({ paths: 'path/for/project' }) 2.pipe(gulp.dest('client/src/lib')); 3 4/* 5 { 6 bowerDirectory: 'path/for/project/bower_components', 7 bowerrc: 'path/for/project/.bowerrc', 8 bowerJson: 'path/for/project/bower.json' 9 } 10*/
Type: boolean
Default: false
Set this to true if you want that the plugin checks every file for existence. If enabled and a file does not exists, the plugin will throw an exception.
(MIT License)
Copyright (c) 2013 Christopher Knötschke cknoetschke@gmail.com
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
Found 3/28 approved changesets -- score normalized to 1
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
license file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More