@radum/stylelint-config NPM

@radum Stylelint config

Personal recommended shareable config for stylelint.

It turns on all the possible errors rules within stylelint based on my own CSS styleguide.

Use it as is or as a foundation for your own config. You can extend or clone and change.

@radum Stylelint config - Installation - Usage - Stylelint no unsupported browser features - Stylelint pattern rules - Extending the config - Deploy - Deploy Locally - Complementary tools - Editor plugins - Editors - Find stylelint rules - Changelog

Installation

npm install -D @radum/stylelint-config stylelint

Usage

This package includes the following configurations:

@radum/stylelint-config - The base code style guide.
@radum/stylelint-config/scss - To be used in addition to "@radum/stylelint-config" configuration by projects that use Sass.

If you've installed @radum/stylelint-config locally within your project, just set your stylelint config to:

{
  "extends": "@radum/stylelint-config"
}

or if you are working on a Scss file:

{
  "extends": [
    "@radum/stylelint-config"
    "@radum/stylelint-config/scss"
  ]
}

This will also set "customSyntax": "postcss-scss".

If you've globally installed @radum/stylelint-config using the -g flag, then you'll need to use the absolute path to @radum/stylelint-config in your config e.g.

{
  "extends": "/absolute/path/to/@radum/stylelint-config"
}

You can also simply use the globally installed configuration name instead of the absolute path:

{ "extends": "@radum/stylelint-config" }

Stylelint no unsupported browser features

Although stylelint-no-unsupported-browser-features is installed is not enforced. You should add your own specific settings.

For example:

"rules": {
	"plugin/no-unsupported-browser-features": [true, {
		"browsers": [
			"last 2 Chrome versions",
			"last 2 Safari versions",
			"last 1 iOS versions",
			"last 2 Firefox versions",
			"last 2 Edge versions"
		],
		"severity": "warning"
	}]
}

Stylelint pattern rules

If you need to enforce naming conventions with pattern rules.

{
  "extends": [
    "@radum/stylelint-config"
    "@radum/stylelint-config/patterns"
  ]
}

Extending the config

Simply 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": "@radum/stylelint-config",
  "rules": {
    "at-rule-no-unknown": [ true, {
      "ignoreAtRules": [
        "extends"
      ]
    }],
    "block-no-empty": null,
    "unit-allowed-list": ["em", "rem", "s"]
  }
}

Deploy

Betwween releases you can raise PRs and merge them, and / or commit straight into main. All of them will be used to generate a changelog and a release.

To deploy a new version merge the final PR and add a release label to it + a label that will be used to do a major, minor, or patch and merge it.

Deploy Locally

Make sure the GITHUB_TOKEN and NPM_TOKEN env vars are set. Also if you have 2FA enabled Auto only works properly if you manually update your local ~/.npmrc file with the NPM token above like this //registry.npmjs.org/:_authToken={TOOKEN VALUE HERE}. Unless I do that it fails to npm publish. Until that is fixed either use CI or this for deployments.

Then run npm run release or npx auto shipit which will run Intuit Auto.

Example:

export GITHUB_TOKEN=...
export NPM_TOKEN=...
npx auto shipit
# This is to remove them from your local
unset GITHUB_TOKEN
unset NPM_TOKEN

Also don't forget to remove the token from your local .npmrc file.

Complementary tools

Editor plugins

Ale: A Vim plugin that supports stylelint.
Flycheck: An Emacs extension that supports stylelint.
linter-stylelint: An Atom plugin for stylelint.
SublimeLinter-stylelint: A Sublime Text plugin for stylelint.
SublimeLinter-contrib-stylelint_d: A Sublime Text plugin for stylelint that run's on daemon.
vscode-stylelint: A Visual Studio Code extension for stylelint.