vscode-markdownlint VS stylelint

There is a very impressive Markdown Linter for VSCode markdownlint. It has built in rules that can be several different ways, it also supports custom rules written in JavaScript.

I'm trying to use flycheck with markdown-markdownlint-cli. Running markdownlint-cli2 via shell and the VSCode Markdownlint Plugin are respecting the configuration file, but flycheck doesn't.

I am seeing this specifically in scss modules linted with stylelint.io which will auto "fix" them to the new spec.

For code consistency there's linters like eslint, stylelint, and others (depending on what you're using backend).

You can automate this with stylelint if you really want to and let the linter handle it.

https://stylelint.io/

Feel free to customise this to your own tastes. See stylelint docs for details.

Check out StyleLint, there's a VSCode plugin and the recommended rule set should do exactly what you're looking for.

stylelint is probably the most popular one. VS Code also has a CSS linter built in if you use that.

Stylelint : While ESLint is a linting tool for your JS code, stylelint is tool for linting your css and scss code.

Link

This is what I use in my projects: Prettier to format the code. Eslint (for react) and Stylelint (for styles). You can additionally use husky to run the above linters and formaters before committing the code, you can also run some tests automatically before every commit, although depending on the number of tests, this can take some time and can be a bit annoying. In GitHub/GitLab, we also have a set of actions on our pipeline to run all of these linters and tests every time we create a merge request or deploy some new code (CI/CD).