grunt-extract-required
Advanced tools
A grunt task to extract commonly required modules in src files, and genenrate a JS code to use as a loader.
Using extract-required inside.
A example grunt task in Gruntfile.js :
...
extract_required: {
lib: {
files: {
'output/core-require.js' : [ 'lib/core/**/*.js' ]
},
options: {
baseDir: 'lib/',
ignore: [ './submodule/**/*' ],
exposeToGlobal: true
}
}
},
...
Specify a base directory to canonicalize relatively loaded module paths.
Specify a glob pattern or name of modules to ignore from the output.
If you want to expose the generated loader function to global, set true (or custom global function name; by default it use require). Otherwise the function will be opened as a CommonJS-style module.
FAQs
Grunt task to extract required modules in src files
The npm package grunt-extract-required receives a total of 7 weekly downloads. As such, grunt-extract-required popularity was classified as not popular.
We found that grunt-extract-required demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket's Rubygems ecosystem support is moving from beta to GA, featuring enhanced security scanning to detect supply chain threats beyond traditional CVEs in your Ruby dependencies.
Research
The Socket Research Team investigates a malicious npm package that appears to be an Advcash integration but triggers a reverse shell during payment success, targeting servers handling transactions.
Security Fundamentals
The Socket Threat Research Team uncovers how threat actors weaponize shell techniques across npm, PyPI, and Go ecosystems to maintain persistence and exfiltrate data.