Security News
Node.js EOL Versions CVE Dubbed the "Worst CVE of the Year" by Security Experts
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
grunt-sassdoc
Advanced tools
SassDoc grunt task.
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, install this plugin with this command:
npm install --save-dev grunt-sassdoc
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks('grunt-sassdoc');
Tip: the load-grunt-tasks module makes it easier to load multiple grunt tasks.
See the Gruntfile in this repo for a full example.
Run this task with the grunt sassdoc
command.
Task targets, files and options may be specified according to the grunt Configuring tasks guide.
Any specified option will be passed through directly to SassDoc, thus you can specify any option that SassDoc supports. See the SassDoc documentation for a list of supported options.
Type: String
Default: null
Path to a view configuration file.
Type: Array
Default: ['public', 'private']
Access levels that should be displayed.
Type: Boolean
Default: false
Enable/disable display of alias items.
Type: Boolean
Default: false
Enable/disable display of SassDoc watermark in footer.
Type: String | Object
Default: './package.json'
Pass your project informations to the generated view.
Either a path to your package.json
or an object.
Following keys will be looked for:
name
version
license
homepage
description
Heads up: If a config file is passed and found, its options will prevail over defauts. Additionnal options passed to the grunt task, will complement it but not override it. You should really manage your options in one place.
// Example with external view configuration file.
grunt.initConfig({
sassdoc: {
default: {
src: 'path/to/sass',
dest: 'path/todocs',
options: {
config: 'path/to/view.json'
}
}
},
});
// Example with passed in options.
grunt.initConfig({
sassdoc: {
default: {
src: 'path/to/sass',
dest: 'path/to/docs',
options: {
display: {
access: ['public', 'private'],
alias: true,
watermark: true
},
package: './package.json'
}
}
},
});
grunt-sassdoc is unlicensed.
FAQs
SassDoc grunt task
The npm package grunt-sassdoc receives a total of 135 weekly downloads. As such, grunt-sassdoc popularity was classified as not popular.
We found that grunt-sassdoc demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 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
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.