We lint everything, including:
scss. We love linting to be as strict as possible.
Everything works for raw files and single file components out of the box. Everything is already configured, so you don't have to.
npm run lintto run everything we have.
typescript. We stick to
wemakecode style. It is just like
standardconfig, but stricter. But, we have some additional checks that make our style even more stricter.
npm run lint:js.
All configuration can be found inside
.eslintrc.js. We also have some specific configuration that is applied for tests only. It is located inside
It extends the default configuration with the new rules that are applied for test frameworks that we use.
jsdocannotation. The rule is simple: if you write
jsdocyou should write a correct one. You may not write them at all (however, that's not good).
These checks are executed together with
We use awesome
stylelintto validate our
scssfiles. We also use strict config here. We stick to
stylelintis not related with
eslintat all. It is a standalone tool. Other plugins for languages like
post-csscan also be installed if you need them.
npm run lint:css.
We also ship a rich set of accessability checks for both
eslintwith the help of:
Please, do not turn it off! Let's make our apps better!
We lint markdown files with
remark-lint. This tool allows us to write consistent documentation and
npm run lint:md.
It checks for multiple things including: ordering, naming, bashism, aliasing, etc.
This is simple tool, but a very useful one. Check out the docs for more information.
Linting can be easily changed to any other styles you like (or forced to use).