eslint-config-canonical
eslint-config-prettier
Our great sponsors
eslint-config-canonical | eslint-config-prettier | |
---|---|---|
7 | 17 | |
570 | 5,216 | |
- | 1.4% | |
8.2 | 6.9 | |
3 months ago | 5 days ago | |
JavaScript | JavaScript | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
eslint-config-canonical
-
ESLint-config-canonical: 1k rules ESLint rules
https://github.com/gajus/eslint-config-canonical
I will repost this every couple of years, as it now has been 8 years since I regularly update this config. For most projects, adopting this is going to be as simple as:
{
- Show HN: Canonical – 1k ESLint rules to automate code conventions
-
semver: v1 vs v1000
It's something that keeps coming up in GitHub issues on my various projects... they point at my project version, which could be v7, v28, v33, and then say "This project versioning is bad." or "This project API is unstable.", etc. and then compare them to projects that are v1, as if that somehow proves their point.
-
Why is is prettier used if eslint can format?
For anyone would would like to migrate from Prettier to ESLint, https://github.com/gajus/eslint-config-canonical covers everything that Prettier does and a lot (a lot) more.
-
ESLint plugin for Storybook
Should we add it to https://github.com/gajus/eslint-config-canonical ?
- eslint-config-canonical: 1,000+ rules ESLint rules
eslint-config-prettier
-
Adding code formatting, linting, pre-commit hooks and beyond...
As I was reading the Prettier documentation I stumbled upon this blob which talks about how to make ESLint and Prettier play nicely with each other. It instructed to install eslint-config-prettier dependency in my project using the command npm install --save-dev eslint-config-prettier. Then I added prettier as part of the .eslintrc.cjs' extends array making prettier dependency part of the linting process. Lastly, I ran its cmd line helper npx eslint-config-prettier path/to/main.js to check if there were any ESLint rules which are unnecessary or would conflict with Prettier. The test results came out fine with no unnecessary or conflicting rules. The use case on how it works and why to use it is mentioned here.
-
It Takes 6 Days to Change 1 Line of Code
I wouldn’t say they’re arguing something completely different. A large subset of linting rules are by nature purely formatting rules. You can enforce line length with either prettier or a linter and both can auto fix the issue.
Because of this things like [`eslint-config-prettier`](https://github.com/prettier/eslint-config-prettier) exist to ensure conflicting eslint formatting rules are disabled if they can be handled by prettier.
-
[AskJS] Does anyone enjoy using Eslint?
If you use Prettier you should disable any and all eslint formatting rules. It's just not worth the hassle trying to make them "compatible". Fortunately there's an easy way to do that with a plugin.
- ESLint and Prettier conflict
-
Looking to improve... Review my code??
Also add this eslint plugin, which makes eslint play nice with prettier: https://github.com/prettier/eslint-config-prettier
-
Any way to disable prettier diagnostics in eslint-lsp
If you don’t care about the diagnostics, you should be using this instead. Prettier even says so.
-
React Library Builder using Rollup.js and Storybook
Linting is an important step in maintaining code quality, The React Library Builder uses ESLint and eslint-config-prettier for linting. You can modify linting rules by overriding them in the .eslintrc file.
-
Setting up ESLint & Prettier in ViteJS
eslint-config-prettier: An ESLint configuration which disables the formatting rules in ESLint that Prettier is going to be responsible for handling, hence avoiding any clashes.
-
Do you use eslint and/or prettier?
You can use both Eslint and Prettier if you care greatly about both linting and code formatting. Prettier had a plugin to disable Eslint's formatting rules.
-
Modern, faster alternatives to ESLint
The eslint-config-prettier package disables all ESLint rules that might conflict with Prettier. This lets us use ESLint configurations without letting it get in the way when using Prettier. We can then use the eslint-plugin-prettier package to integrate Prettier rules into ESLint rules. Finally, we must set the Prettier rules in the ESLint configuration file. Add the following configuration to the .eslintrc file in the root directory of the application:
What are some alternatives?
eslint-plugin-unicorn - More than 100 powerful ESLint rules
eslint-config-google - ESLint shareable config for the Google JavaScript style guide
quick-lint-js - quick-lint-js finds bugs in JavaScript programs
eslint-plugin-prettier - ESLint plugin for Prettier formatting
typescript-eslint - :sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript
react-webpack-5-tailwind-2 - React 17 Boilerplate with Webpack 6, Tailwind 2, using babel, SASS/PostCSS, HMR, dotenv and an optimized production build
eslint-plugin-canonical - ESLint rules for Canonical ruleset.
webpack-react-typescript-starter - React App with Typescript, using webpack5 and styled-components
roarr - JSON logger for Node.js and browser.
prettier-eslint-cli - CLI for prettier-eslint
eslint-plugin-storybook - 🎗Official ESLint plugin for Storybook
vitte - A non SSR Starter Template using Svelte, Vite, Tailwind JIT. And Routify.