stylelint
ESLint
Prettier
TSLint
BEM
Prepros
Next.js
PostCSS
SonarQube
Codacy
CodeClimate
Checkmarx
Coverity Scan
Snyk
ReSharper
PyCharm
SonarQube, a core component of the Sonar solution, is an open source, self-managed tool that systematically helps developers and organizations deliver Clean Code. SonarQube integrates into the developers' CI/CD pipeline and DevOps platform to detect and help fix issues in the code while performing continuous inspection of projects.
Supported by the Sonar Clean as You Code methodology, only code that meets the defined quality standard can be released to production. SonarQube analyzes the most popular programming languages, frameworks, and infrastructure technologies and supports over 5,000 Clean Code rules.
Trusted by 7 million developers and 400,000 organizations globally to clean more than half a trillion lines of code, Sonar has become integral to delivering better software.
Explore our pricing and request an evaluation: https://www.sonarsource.com/plans-and-pricing/
stylelint SonarQubeBased on our record, stylelint seems to be a lot more popular than SonarQube. While we know about 24 links to stylelint, we've tracked only 1 mention of SonarQube. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
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 / 3 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 / 3 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 / 12 months 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
I use StyleLint (https://stylelint.io/) to lint my css/scss. I don't think that's a rule, but writing a custom rule isn't too tough. And you can use the vscode extension - https://marketplace.visualstudio.com/items?itemName=stylelint.vscode-stylelint. Source: about 1 year ago
Even for Java, C# and JS we do enforce such kind of rules, e.g. https://sonarqube.org. - Source: Hacker News / over 1 year ago
ESLint - The fully pluggable JavaScript code quality tool
Codacy - Automatically reviews code style, security, duplication, complexity, and coverage on every change while tracking code quality throughout your sprints.
Prettier - An opinionated code formatter
CodeClimate - Code Climate provides automated code review for your apps, letting you fix quality and security issues before they hit production. We check every commit, branch and pull request for changes in quality and potential vulnerabilities.
TSLint - An extensible static analysis linter for the TypeScript language
Checkmarx - The industry’s most comprehensive AppSec platform, Checkmarx One is fast, accurate, and accelerates your business.