Gathering detailed insights and metrics for source-deps
Gathering detailed insights and metrics for source-deps
Gathering detailed insights and metrics for source-deps
Gathering detailed insights and metrics for source-deps
A tool for automatically discovering and "sourcing" your dependency packages from Bower and NPM.
npm install source-deps
Typescript
Module System
Node Version
NPM Version
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
4 Stars
80 Commits
2 Forks
1 Branches
1 Contributors
Updated on Feb 04, 2022
Latest Version
0.3.9
Package Id
source-deps@0.3.9
Size
5.48 kB
NPM Version
2.14.2
Node Version
0.12.7
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
A tool for automatically discovering and "sourcing" your dependency packages from Bower and NPM and any other packagers.
1npm install --save-dev source-deps
1var deps = require('source-deps'), 2 concat = require('gulp-concat'); 3 4gulp.task('bundle', function () { 5 var depFiles = deps({ 6 packagers: ['bower', 'npm'], 7 includeDevPackages: false, 8 logOutput: false, 9 overrides: { 10 angular: 'lib/angular.min.js' 11 }, 12 ignore: ['normalize.css'], 13 order: [ 14 'angular', 15 'angular-mocks' 16 ], 17 include: [ 18 'some-package-apparently-not-listed-as-dependency' 19 ], 20 recursive: true // Pull in dependencies of dependencies (in proper order too :) 21 }); 22 gulp.src(depFiles) 23 .pipe(concat(['src/**/*.js'])) 24 .pipe(gulp.dest('all.js')); 25});
This example pulls in all production dependencies from package.json
and bower.json
.
Overrides tells it where to find dist files for a library where the automatic guessing is not working.
It is very important that you make sure each dependency package has correct paths to the dist files.
1deps({ 2 packagers: ['bower', 'npm'], 3 logOutput: true 4})
This will show you how many files get pulled in as well as which packages are likely not being pulled properly.
As of 0.2.5
you can control the ordering of your dependant files now! Very helpful, like so.
1var deps = require('source-deps'), 2 depFiles = deps({ 3 packagers: ['bower'], 4 order: [ 5 'angular', 6 'angular-mocks', 7 'angular-animate' 8 ] 9 });
This will happily prevent your dependencies from being loaded out of proper resolution order :)
And now you can ignore certain packages by just adding them to the ignore
option like so:
1 2var deps = require('source-deps'), 3 depFiles = deps({ 4 packagers: ['bower'], 5 order: [ 6 'angular', 7 'angular-mocks' 8 ], 9 ignore: [ 10 'angular-animate' 11 ] 12 });
This is for a number of odd situations where there is a package present that is either:
A) Not listed as a dependency
B) Ignored already
C) Ignored by a future feature that allows for exclusion patterns
... and needs to be included anyway. In other words it overrides any exclusions.
1 2depFiles = deps({ 3 packagers: ['bower'], 4 ignore: ['said-package'], 5 include: ['said-package'] // Takes priority 6}); 7
Oh yeah... this does exactly what you think it does. Bye, bye RequireJS shims on the frontend.
1 2depFiles = deps({ 3 packagers: ['bower'], 4 recursive: true 5});
order
, ignore
, and include
.order
to resolve anything that pulls in too early / too late as a result of overlapping secondaries amongst packages.No vulnerabilities found.
Reason
license file detected
Details
Reason
0 existing vulnerabilities detected
Reason
binaries present in source code
Details
Reason
Found 0/30 approved changesets -- score normalized to 0
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
no SAST tool detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
project is not fuzzed
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