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-jshint
Advanced tools
Run JSHint 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-jshint --save-dev
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks( 'grunt-codeblock-jshint' );
In your project's Gruntfile, add a section named 'codeblock-jshint'
to the data object passed into grunt.initConfig()
.
grunt.initConfig({
'codeblock-jshint': {
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 JSHint reporter, or else a custom reporter function to use when logging the output from JSHint
Type: Object
An object specifying JSHint 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.
grunt.initConfig({
'codeblock-jshint': {
src: './path/to/some/markdown/files/**/*.md'
}
});
In this example, two different directories of markdown files are scanned, and results from one of them are logged with a custom JSHint reporter
grunt.initConfig({
'codeblock-jshint': {
slides: {
src: [
'path/to/slides/**/*.md',
'other/slide/particular-slide.md'
]
},
notes: {
options: {
reporter: require( 'jshint-stylish' )
},
src: 'path/to/notes/**/*.md'
}
},
});
In this example, several non-default JSHint options are passed in and will be used when checking the specified files.
grunt.initConfig({
'codeblock-jshint': {
options: {
jshintOptions: {
curly: true,
undef: true
}
},
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.
jshintOptions
option now enables custom JSHint configuration options to be specifiedlang
option is now configurable with a regex or stringFAQs
Run JSHint against code snippets within Markdown slides
The npm package grunt-codeblock-jshint receives a total of 0 weekly downloads. As such, grunt-codeblock-jshint popularity was classified as not popular.
We found that grunt-codeblock-jshint 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.