Gathering detailed insights and metrics for stylelint-config-rivet
Gathering detailed insights and metrics for stylelint-config-rivet
Gathering detailed insights and metrics for stylelint-config-rivet
Gathering detailed insights and metrics for stylelint-config-rivet
A stylelint configuration set for Rivet-related projects
npm install stylelint-config-rivet
Typescript
Module System
Node Version
NPM Version
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
BSD-3-Clause License
2 Commits
7 Watchers
11 Branches
6 Contributors
Updated on May 13, 2019
Latest Version
1.0.0
Package Id
stylelint-config-rivet@1.0.0
Unpacked Size
6.01 kB
Size
2.88 kB
File Count
5
NPM Version
6.5.0
Node Version
11.9.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
2
1
This package extends stylelint-config-standard
(see stylelint documentation) with rules specific to creating projects within the Rivet extended universe.
You can include this package in your project by installing it via npm
:
npm install --save-dev stylelint-config-rivet
Next you will need to setup the configuration for your project using one of the following options:
package.json
{
"stylelint": {
"extends": "stylelint-config-rivet"
}
}
.stylelintrc
{
"extends": "stylelint-config-rivet"
}
stylelint.config.js
module.exports = {
'extends': 'stylelint-config-rivet'
}
Many traditional Rivet projects use Gulp
to handle their build processes. This stylelint
configuration is ideal for integrating with Gulp
.
First, you will need to make sure that Gulp
and its stylelint
build tool are installed.
npm install --save-dev gulp gulp-stylelint
Next, you will need to incorporate this into your Gulp
setup. Below is an example gulpfile.js
, which shows how to include the build tool in your file and how to write the linting task.
const { src } = require("gulp");
const stylelint = require("gulp-stylelint");
function lintSassWatch() {
return src("src/sass/**/*.scss")
.pipe(stylelint({
failAfterError: false,
reporters: [
{formatter: 'string', console: true}
]
}));
}
function lintSassBuild() {
return src("src/sass/**/*.scss")
.pipe(stylelint({
reporters: [
{formatter: 'string', console: true}
]
}));
}
We recommend writing separate functions for linting build
versus watch
tasks. For lint functions related to your watch
tasks we recommend including the failAfterError: false
option. This option defaults to true
, and will cause your watch process to fail if it encounters an error. While this functionality is desirable for a build
task, it can be more annoying than helpful for a watch
task.
Finally, there are a number of Rivet-based applications which rely on webpack
to bundle their code.
First, you will need to make sure that the stylelint
plugin for webpack
is installed. There is a different stylelint-loader
available; however, it does not allow for @imports
, and will therefore only lint the main file for each require/entry
(see plugin documentation).
npm install --save-dev stylelint-webpack-plugin
Next, you will need to setup stylelint
in your webpack
configuration. Below is an example webpack.config.js
file.
const stylelint = require('stylelint-webpack-plugin');
module.exports = {
// ...
plugins: [
new stylelint({ failOnError: true }),
],
// ...
}
It's important to note that when using transpilers (such as babel
) and linting tools, the order they are listed in usually matters as you want to ensure that your code is linted before being transpiled.
Stylelint has integrations available for most of the major, modern code editors.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 0/2 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
33 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More