Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
stylelint-config-recommended
Advanced tools
The stylelint-config-recommended package is a shareable configuration for Stylelint, a popular CSS linter. It provides a set of recommended rules to help you enforce consistent and error-free CSS code. This package includes a basic set of rules that catch common errors and enforce best practices.
Basic Configuration
This feature allows you to extend the recommended configuration in your Stylelint configuration file. By doing so, you inherit a set of predefined rules that help maintain code quality and consistency.
{
"extends": "stylelint-config-recommended"
}
Catching Syntax Errors
This feature includes rules that catch common syntax errors such as empty blocks and invalid hex colors. These rules help prevent mistakes that could lead to broken or inconsistent styles.
{
"rules": {
"block-no-empty": true,
"color-no-invalid-hex": true
}
}
Enforcing Best Practices
This feature enforces best practices by including rules that prevent duplicate properties and font family names. These rules help ensure that your CSS is clean and maintainable.
{
"rules": {
"declaration-block-no-duplicate-properties": true,
"font-family-no-duplicate-names": true
}
}
The stylelint-config-standard package provides a more comprehensive set of rules compared to stylelint-config-recommended. It includes additional rules for stylistic issues and best practices, making it suitable for projects that require stricter code quality enforcement.
The stylelint-config-sass-guidelines package is tailored for Sass projects and follows the guidelines set by Sass Guidelines. It includes rules specific to Sass syntax and best practices, making it a good choice for projects that use Sass.
The stylelint-config-prettier package turns off all rules that are unnecessary or might conflict with Prettier, a code formatter. This package is useful if you want to use Stylelint for catching errors and Prettier for formatting.
The recommended shareable config for Stylelint.
It turns on most of the Stylelint rules that help you avoid errors.
You can use this as a foundation for your own config, but we suggest most people use our standard config instead which extends this config and adds a few more rules to enforce common conventions.
npm install stylelint-config-recommended --save-dev
Set your stylelint
config to:
{
"extends": "stylelint-config-recommended"
}
Add a "rules"
key to your config, then add your overrides and additions there.
For example, to change the at-rule-no-unknown
rule to use its ignoreAtRules
option, turn off the block-no-empty
rule, and add the unit-allowed-list
rule:
{
"extends": "stylelint-config-recommended",
"rules": {
"at-rule-no-unknown": [
true,
{
"ignoreAtRules": ["extends"]
}
],
"block-no-empty": null,
"unit-allowed-list": ["em", "rem", "s"]
}
}
14.0.1
funding
field in package.json
.FAQs
Recommended shareable config for Stylelint
The npm package stylelint-config-recommended receives a total of 3,420,586 weekly downloads. As such, stylelint-config-recommended popularity was classified as popular.
We found that stylelint-config-recommended demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.