Gathering detailed insights and metrics for tracksale-grunt-contrib-requirejs
Gathering detailed insights and metrics for tracksale-grunt-contrib-requirejs
Gathering detailed insights and metrics for tracksale-grunt-contrib-requirejs
Gathering detailed insights and metrics for tracksale-grunt-contrib-requirejs
npm install tracksale-grunt-contrib-requirejs
Typescript
Module System
Min. Node Version
Node Version
NPM Version
40.9
Supply Chain
90.7
Quality
69.2
Maintenance
100
Vulnerability
97
License
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
504 Stars
91 Commits
98 Forks
22 Watchers
2 Branches
21 Contributors
Updated on Feb 21, 2025
Latest Version
0.4.6
Package Id
tracksale-grunt-contrib-requirejs@0.4.6
Size
2.77 kB
NPM Version
2.7.4
Node Version
0.12.2
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
1
Optimize RequireJS projects using r.js.
This plugin requires Grunt ~0.4.0
If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
1npm install grunt-contrib-requirejs --save-dev
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
1grunt.loadNpmTasks('grunt-contrib-requirejs');
This plugin was designed to work with Grunt 0.4.x. If you're still using grunt v0.3.x it's strongly recommended that you upgrade, but in case you can't please use v0.3.3.
Run this task with the grunt requirejs
command.
Task targets and options may be specified according to the grunt Configuring tasks guide.
For a full list of possible options, see the r.js example build file.
The done option is an optional hook to receive the r.js build output. The first argument is the grunt async callback that you are required to call if you provide the done hook. This informs grunt that the task is complete. The second parameter is the build output from r.js.
1requirejs: { 2 compile: { 3 options: { 4 baseUrl: "path/to/base", 5 mainConfigFile: "path/to/config.js", 6 name: "path/to/almond", // assumes a production build using almond 7 out: "path/to/optimized.js" 8 } 9 } 10}
1requirejs: { 2 compile: { 3 options: { 4 baseUrl: "path/to/base", 5 mainConfigFile: "path/to/config.js", 6 done: function(done, output) { 7 var duplicates = require('rjs-build-analysis').duplicates(output); 8 9 if (Object.keys(duplicates).length > 0) { 10 grunt.log.subhead('Duplicates found in requirejs build:'); 11 for (var key in duplicates) { 12 grunt.log.error(duplicates[key] + ": " + key); 13 } 14 return done(new Error('r.js built duplicate modules, please check the excludes option.')); 15 } else { 16 grunt.log.success("No duplicates found!"); 17 } 18 19 done(); 20 } 21 } 22 } 23}
done
.Task submitted by Tyler Kellen
This file was generated on Fri Apr 25 2014 15:35:54.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
Found 4/30 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
project is not fuzzed
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