stylelint.io | The source of the Stylelint website | Plugin library

You are extending the stylelint-config-concentric-order community config. This config includes and configures the stylelint-order community plugin. You can find the order of the properties in the repo on GitHub.

You can see Stylelint errors in VS Code using the official Stylelint extension.

And you can have the extension automatically fix problems on save, which will include the order of your properties, using the editor.codeActionsOnSave configuration property:

You configured it correctly.

The stylelint-config-standard-scss package is separate from the stylelint one and has its own CHANGELOG. Version 2.0.0 of the package turned on a dozen new rules. Additionally, the package updated the two shared configs it extends which, in turn, have their own CHANGELOGs:

• stylelint-config-standard
• stylelint-config-recommended-scss

Both of these configs turned on new rules in their last major releases.

In summary, by updating to version 2.0.0 of stylelint-config-standard-scss over two dozen new rules were turned on.

Ideally, you should update your codebase to fix the problems. Alternatively, you can extend the config and turn off any rules you don't want.

For example, to turn off the alpha-value-notation rule:

so - when it says Unknown rule no-invalid-position-at-import-rule I focused too hard on the no-invalid-position-at-import-rule when what I should have focused on it the Unknown rule part.

Stylelint was saying it did not know this rule - why did it not know this rule? Because we had recently updated our stylelint config but not our stylelint version, so there were rules in the configuration that stylelint did not know about.

Those are not errors. Those are warnings. This will happen if you are using npm@6 and install with --save-dev when you don't already have a package.json file. The results are normal if you don't intend to have a package.json file in your project, but that does mean that your dependencies are not being saved in package.json for future installation. npm@6 will create a package-lock.json file however.

In general, if you're just messing around to get familiar with stylelint, you can ignore the warnings. If you are scaffolding a project, you probably want to create a package.json first. To do that quickly, run npm init.

If you update to npm@7, the warnings do not show up and npm creates the package.json file for you instead. However it will only contain the devDependencies entry when it is created. That may be OK depending on your use case. If in doubt, run npm init first.

This looks like a valid warning. You should be able to fix it by removing the semicolon from the highlighted line.

Replace:

Your stylelint configuration object in your .stylelintrc file should be:

If I understood correctly you can just set the font families directly to .theme-a and .theme-b e.g.:

The default formatter for the stylelint Node API is "json", whereas the stylelint CLI uses the "string" formatter.

You can use the formatter property to use the "string" formatter when using the Node API, like so:

Is there a stylelint rule that can enforce a selector and attribute to be on the same line if there is only one attribute.

Not yet.

The declaration-block-single-line-max-declarations rule will get you halfway there. For example: