Based on our record, Prettier should be more popular than EditorConfig. It has been mentiond 289 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.
In short semi-columns in JavaScript helps reduce the surface for bugs in poorly maintained code bases, and provides clearer intent to formatters such as prettier. - Source: dev.to / 3 months ago
For years, I've been prettier's biggest fan... Introducing it to every codebase at a new role, instantly adding it to any new repository, installing additional plugins such as tailwind or xml and of course, ensuring the "Format on save" option is switched on. - Source: dev.to / 11 days ago
If you’ve ever set up a JavaScript or TypeScript project, chances are you've spent way too much time configuring ESLint, Prettier, and their dozens of plugins. We’ve all been there — fiddling with .eslintrc, fighting with formatting conflicts, and installing what feels like half the npm registry just to get decent code quality tooling. - Source: dev.to / about 2 months ago
Use tools like Prettier to reformat code when things get messy. - Source: dev.to / 2 months ago
Unfortunately, this did mean that configuration began to sprawl. At this point, I had configurations not just for Vite (shared with Vitest) and tsc, but also for Prettier, ESLint and even ShellCheck. Many of these files had shared settings that needed to match each other. This was somewhat manageable, until Vite was also in the mix. - Source: dev.to / 6 months ago
FWIW: EditorConfig isn't a ".net ecosystem" thing but works across a ton of languages, editors and IDEs: https://editorconfig.org/ Also, rather than using GitHub Actions to validate if it was followed (after branch was pushed/PR was opened), add it as a Git hook (https://git-scm.com/docs/githooks) to run right before commit, so every commit will be valid and the iteration<>feedback loop gets like 400% faster as... - Source: Hacker News / about 1 month ago
Added support for EditorConfig, .env, and HOCON validation. - Source: dev.to / 10 months ago
There is always .editorconfig [1] to setup indent if you have a directory of files. In places where it really matters (Python) I'll always comment with what I've used. [1] https://editorconfig.org/. - Source: Hacker News / about 1 year ago
.editorconfig helps maintain consistent coding styles for multiple developers working on the same project across various editors and IDEs. Find more information on the EditorConfig website if you’re curious. - Source: dev.to / about 1 year ago
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 / about 1 year ago
ESLint - The fully pluggable JavaScript code quality tool
Tailwind CSS - A utility-first CSS framework for rapidly building custom user interfaces.
Standard JS - DevOps, Build, Test, Deploy, and Code Review
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.
Next.js - A small framework for server-rendered universal JavaScript apps
pre-commit by Yelp - A framework for managing and maintaining multi-language pre-commit hooks