Research
Security News
Threat Actor Exposes Playbook for Exploiting npm to Build Blockchain-Powered Botnets
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
grunt-codeblock-jscs
Advanced tools
Run JSCS against code snippets within Markdown slides
This plugin requires Grunt ~0.4.5
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-codeblock-jscs --save-dev
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks( 'grunt-codeblock-jscs' );
In your project's Gruntfile, add a section named 'codeblock-jscs'
to the data object passed into grunt.initConfig()
.
grunt.initConfig({
'codeblock-jscs': {
options: {
// Task-specific options go here
},
your_target: {
// Target-specific file lists and/or options go here
}
},
});
Type: String|Function
The path to a custom JSCS reporter, or else a custom reporter function to use when logging the output from JSCS
Type: Object
An object specifying JSCS rules that will be used when validating the code tokens
In this example, the default reporter is used, and all markdown files within
the provided directory are scanned for code blocks to lint. Since there are no JSCS "defaults," you must provide a JSCS options object (in this case reading in from a .jscsrc
).
grunt.initConfig({
'codeblock-jscs': {
options: {
jscsOptions: grunt.file.readJSON( '.jscsrc' )
},
src: './path/to/some/markdown/files/**/*.md'
}
});
In this example, two different directories of markdown files are scanned, and the results from each are determined with different JSCS presets
grunt.initConfig({
'codeblock-jscs': {
slides: {
options: {
preset: 'jquery'
},
src: [
'path/to/slides/**/*.md',
'other/slide/particular-slide.md'
]
},
notes: {
options: {
preset: 'google'
},
src: 'path/to/notes/**/*.md'
}
},
});
In this example, a preset is overridded with the specified JSCS options.
grunt.initConfig({
'codeblock-jscs': {
options: {
jscsOptions: {
preset: 'jquery',
// Disable some rules
validateQuoteMarks: null,
requireCamelCaseOrUpperCaseIdentifiers: null
}
},
src: './path/to/some/markdown/files/**/*.md'
}
});
Lint and test your code using the npm test
command. In lieu of a formal styleguide, JSHint and JSCS are in place to ensure code style consistency. Add unit tests for any new or changed functionality.
FAQs
Run JSCS against code snippets within Markdown slides
The npm package grunt-codeblock-jscs receives a total of 0 weekly downloads. As such, grunt-codeblock-jscs popularity was classified as not popular.
We found that grunt-codeblock-jscs 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.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
Security News
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.