eslint-config-prettier
eslint-config-prettier copied to clipboard
prettier
Turns off all rules that are unnecessary or might conflict with Prettier.
Eslint announced a new config spec. https://eslint.org/docs/latest/user-guide/configuring/configuration-files-new According to [eslint's official blog](https://eslint.org/blog/2022/08/new-config-system-part-2/), though backward compatibility was taken care of, not all shareable configs continue to work with the new config...
Spinning out of https://github.com/JoshuaKGoldberg/dot-com/pull/140 and a direct conversation with @lydell: now that most ESLint recommended configs/plugins no longer enable formatting rules, it seems that `eslint-config-prettier` isn't necessary in most projects....
Since formatting rules have been deprecated from core ESLint and moved to `@stylistic/eslint-plugin`, this PR adds support for all the same rules in `@stylistic/eslint-plugin`. Despite its name, `@stylistic/eslint-plugin` still has...
I just update the installation commands in the README.md adding yarn, pnpm, and bun options, "with shell code block".
eslint and typescript-eslint have moved their stylistic rules to @stylistic/eslint-plugin. These are the new rules I believe that need to be turned off: - `@stylistic/block-spacing` - `@stylistic/brace-style` - `@stylistic/comma-dangle` -...
I don't understand how it conflicts with Prettier. It's been enabled in Prettier codebase since the rule released. https://github.com/prettier/prettier/pull/12469 I never see any conflicts. Quote from https://github.com/prettier/eslint-config-prettier/pull/269#issuecomment-1807580963 > Sure, here,...
I have the following set of rules: ```javascript import importPlugin from "eslint-plugin-import" import prettierPlugin from "eslint-plugin-prettier" export default [ { plugins: { "import": importPlugin, "prettier": prettierPlugin, }, rules: { "prettier/prettier":...
