EditorConfig
Prettier
ESLint
pre-commit by Yelp
SonarQube
Standard JS
unpkg
RuboCop
CodeClimate
SonarQube
Codacy
ESLint
CodeFactor.io
Coveralls
SensioLabs Insight
Source Insight
EditorConfig CodeClimateBased on our record, EditorConfig should be more popular than CodeClimate. It has been mentiond 80 times since March 2021. 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.
These are tools that you need to add. But the most elemental code formatting is not here, it is in the widely supported .editorconfig file. - Source: dev.to / 14 days ago
Hello, Maybe you should check this project: https://editorconfig.org/ Regards,. - Source: Hacker News / 4 months ago
Editorconfigchecker. A linter that checks files for compliance with editorconfig rules. Another linter that helps maintain consistency in the format of all files. - Source: dev.to / 5 months ago
Oh, yeah, we had that issue too and solved it pretty successfully with `.editorconfig` (shareable between VScode and IntelliJ, https://editorconfig.org/) combined with `prettier`. Each IDE is configured to: - Not reformat code on its own - Ignore whitespace - Run `prettier` as a pre-commit hook Those settings are saved to `.editorconfig` where possible, or to each IDE's repo-specific folder (e.g. `.idea`). Then in... - Source: Hacker News / 6 months ago
I am aware of .editorconfig, and one day that may be the correct answer but the specification does not support every element of the styles of both oss and css. Source: 7 months ago
Codeclimate.com — Automated code review, free for Open Source and unlimited organisation-owned private repos (up to 4 collaborators). Also free for students and institutions. - Source: dev.to / over 1 year ago
Want to know how to enforce allowing only high-quality software into production? Check out this post on how to use CodeClimate can help you do just that! #DevOps #SoftwareDeveloper #softwaredevelopment #SoftwareEngineering #webdevelopment #codequality. Source: almost 2 years ago
Ideally, software can quickly go from development to production. Continuous deployment and delivery are some processes that make this possible. Continuous deployment means establishing an automated pipeline from development to production while continuous delivery means maintaining the main branch in a deployable state so that a deployment can be requested at any time. Predecos uses these tools. When a commit goes... - Source: dev.to / almost 2 years ago
The new code should not drop existing code coverage I've found in practice mainly catches changes to existing code that lack proper updates to existing tests. Our company uses Code Climate for these checks, so we don't have to manage / write our own tooling for this purpose. Source: about 2 years ago
TL;DR: Using static analysis tools helps by giving objective ways to improve code quality and keeps your code maintainable. You can add static analysis tools to your CI build to fail when it finds code smells. Its main selling points over plain linting are the ability to inspect quality in the context of multiple files (e.g. Detect duplications), perform advanced analysis (e.g. Code complexity), and follow the... - Source: dev.to / almost 3 years ago
Prettier - An opinionated code formatter
SonarQube - SonarQube, a core component of the Sonar solution, is an open source, self-managed tool that systematically helps developers and organizations deliver Clean Code.
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.
pre-commit by Yelp - A framework for managing and maintaining multi-language pre-commit hooks
CodeFactor.io - Automated Code Review for GitHub & BitBucket