eslint-config-prettier
prettier-eslint
Our great sponsors
eslint-config-prettier | prettier-eslint | |
---|---|---|
17 | 6 | |
5,216 | 3,929 | |
1.4% | 0.7% | |
6.9 | 6.5 | |
6 days ago | 3 days ago | |
JavaScript | JavaScript | |
MIT License | 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-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:
prettier-eslint
-
help with create-react-app and eslint/prettier
Use the other one, prettier-eslint this is so that the code goes through Prettier before ESLint and not the other way around causing it to show issues that will be fixed once ESLint fixes it.
- Prettier and how to get most out of it
-
Why can't they tho?
Same, I can't stand some of prettier's opinions/style conversions and they refuse to add more options to their config file, so people literally have to make an entirely separate plugin just to deal with the issue of its config not being able to match your eslint config.
-
Setting up ESLint & Prettier in ViteJS
prettier-eslint
-
I always have a hard time configuring my projects
side note: you can use prettier-eslint (as opposed to the prettier eslint plugin) which runs prettier and then eslint --fix. that way you won't get annoyed by a shit ton red lines from eslint linting with prettier.
-
Boilerplate with React 17, Webpack 5, Tailwind 2, using babel, sass, with a hot dev server and an optimized production build
And I just ripped out my prettierrc/prettier recently, and still need some tweaking in this area, and might even add it it back. After looking at that plugin, it looks like it just DISABLES things in ESLint that Prettier handles, so you might have to add the prettier script and a .prettierrc config file. At least that is how I understand it. I was just looking at prettier's docs and saw this though - https://github.com/prettier/prettier-eslint, which seems like it might be what you are looking for.
What are some alternatives?
eslint-config-google - ESLint shareable config for the Google JavaScript style guide
twin.examples - Packed with examples for different frameworks, this repo helps you get started with twin a whole lot faster.
eslint-plugin-prettier - ESLint plugin for Prettier formatting
prettier-eslint-cli - CLI for prettier-eslint
react-webpack-5-tailwind-2 - React 17 Boilerplate with Webpack 6, Tailwind 2, using babel, SASS/PostCSS, HMR, dotenv and an optimized production build
webpack-react-typescript-starter - React App with Typescript, using webpack5 and styled-components
linters - CSSSR's linting configs for Prettier and ESLint.
vitte - A non SSR Starter Template using Svelte, Vite, Tailwind JIT. And Routify.
prettier-plugin-apex - Code formatter for the Apex Programming Language