
Security News
vlt Launches "reproduce": A New Tool Challenging the Limits of Package Provenance
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
grunt-vulcanize
Advanced tools
Grunt task for Polymer's Vulcanize
This plugin requires Grunt ~0.4.1
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:
npm install grunt-vulcanize --save-dev
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks('grunt-vulcanize');
In your project's Gruntfile, add a section named vulcanize
to the data object passed into grunt.initConfig()
.
grunt.initConfig({
vulcanize: {
options: {
// Task-specific options go here.
},
your_target: {
// Target-specific file lists and/or options go here.
},
},
})
Type: Boolean
Default value: false
Extract inline <script>
blocks into a separate file. Maps directly to https://github.com/Polymer/vulcanize#content-security-policy
Type: Boolean
Default value: false
The opposite of csp
mode: inline all scripts and stylesheets.
Type: Boolean
Default value: false
Strip comments and empty text nodes from output.
Type: Array[String]
Default value: []
An array of strings that will be used as RegExp
s to filter matching imports from vulcanization.
This option should be used if multiple vulcanizations would share imports, as they could no longer be deduplicated in
their vulcanized forms.
In this example, the default options are used to vulcanize index.html
into build.html
.
Please see https://github.com/Polymer/vulcanize#example for more information.
grunt.initConfig({
vulcanize: {
options: {},
files: {
'build.html': 'index.html'
},
},
})
In this example, custom options are used to apply Content Security Policy settings on the vulcanization of index.html
into build-csp.html
.
Please see https://github.com/Polymer/vulcanize#content-security-policy for more information
grunt.initConfig({
vulcanize: {
options: {
csp: true
excludes: {
imports: [
"polymer.html"
]
}
},
files: {
'build-csp.html': 'index.html'
},
},
})
Contributions to this project must follow the guidlines of the Contributor License Agreement
(Nothing yet)
FAQs
Grunt plugin for Polymer's Vulcanize. Compatible with Polymer 1.0
The npm package grunt-vulcanize receives a total of 143 weekly downloads. As such, grunt-vulcanize popularity was classified as not popular.
We found that grunt-vulcanize demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers 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.
Security News
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.