There are more linting tools that I won't go into deeply, but you can integrate them with lint-staged. For example, you can lint your CSS content with Stylelint, or even lint your README files with markdownlint, etc. - Source: dev.to / 17 days ago

Another common way to extend configs in linters is using the extends key in the configuration file. Let's take StyleLint as an example:. - Source: dev.to / 4 months ago

Stylelint is similar to ESLint, but its focus is on styling rather than JavaScript. It helps you find errors in style files, such as old syntax or empty classes. We will also incorporate stylelint-config-clean-order to sort your style rules and group them consistently across the entire codebase. - Source: dev.to / 4 months ago

As the property is still experimental, stylelint does not recognize it yet at the time of writing this, so let's explicitly disable the property-no-unknown rule only where we use it by adding a stylelint-disable comment and re-enable it afterwards. - Source: dev.to / about 1 year ago

Run static analysis e.g. Lint with lockfile-lint, Stylelint, ESLint, check for unimported files using unimported, and identify potential security vulnerabilities. Source: about 1 year ago

React Testing Library - https://testing-library.com/docs/react-testing-library/intro/. - Source: dev.to / 13 days ago

React Testing Library: provides utilities to make testing easier. - Source: dev.to / about 1 month ago

Since we are testing the front-end, we will also rely on the React Testing Library, which provides support for rendering components and custom queries in the DOM. - Source: dev.to / about 2 months ago

It’s not to say 100% coverage is the way to go, but at least some functional testing with something like react-testing-library and cypress can save a lot of time. - Source: dev.to / 5 months ago

If you happen to be using React Testing Library in your project, you'll need to keep the jsdom dev dependency installed. - Source: dev.to / 5 months ago