You can make git blame ignoring certain commits, which do only mass reformatting etc.: Create a file .git-blame-ignore-revs like: # Format commit 1 SHA: 1234af5….. # Format commit 2 SHA: 2e4ac56….. Then do git config blame.ignoreRevsFile .git-blame-ignore-revs , so that you don’t have to use the –ignore-revs-file option every time with git blame. Upvote https://github.com/github/feedback/discussions/5033 … Read more
prettier/@typescript-eslint has been removed in eslint-config-prettier v8.0.0. Just remove it from your ESLint config file. The only entry in extends that is needed now for Prettier and ESLint to not conflict is “prettier” (make sure it’s the last one in extends).
I’ve had very similar error, but in my case default VSCode TypeScript formatter was messing with braces. In .vscode/settings.json add: “javascript.format.insertSpaceAfterOpeningAndBeforeClosingEmptyBraces”: false, “typescript.format.insertSpaceAfterOpeningAndBeforeClosingEmptyBraces”: false, You might also find useful option: “[typescript]”: { “editor.defaultFormatter”: “dbaeumer.vscode-eslint” }
Just found solution. Following command will target both ts and tsx: prettier –write “./src/**/*.{ts,tsx}” Prettier is using Glob syntax which is syntax similar to Regex, used in shell. See GLOB syntax details: https://github.com/isaacs/node-glob/blob/master/README.md#glob-primer
Prettier is a peer dependency of @vue/eslint-config-prettier so you need to add it to your own dependencies: npm install –save-dev prettier
I’m trying to get my VS Code to run ESLint and Prettier together properly as well. Then VSCode 1.44 (March 2020) would highlight another difference between codeActionsOnSave and formatOnSave: Explicit ordering for editor.codeActionsOnSave You can now set editor.codeActionsOnSave to an array of code actions to execute in order. You can use this to guarantee that … Read more
In Prettier < 2.4.0: Add jsxBracketSameLine: true in your Prettier settings. In Prettier >= 2.4., jsxBracketSameLine is deprecated, so: Add bracketSameLine: true in your Prettier settings. You can refer to the official documentation for more information.
Prettier has caused this regression in their 1.13.0 update which occurred today. Downgrade to the previous version to fix this error: npm install –save-dev prettier@1.12.0 npm run dev That should do the trick.
Short answer: I needed: “editor.formatOnSave”: false, “javascript.format.enable”: false. I finally found the magical combination of settings, thanks to this thread from Wes Bos on Twitter. I was right in my suspicion that there seem to be multiple conflicting formatters. Though I’m not sure what they actually are, I was able to turn off all but … Read more
There is an incompatibility between prettier 3 and eslint-plugin-prettier 4. You can fix this by using version 5 of eslint-plugin-prettier: yarn add -D eslint-plugin-prettier@5.0.0 or npm install –save-dev eslint-plugin-prettier@5.0.0 Official issue: https://github.com/prettier/eslint-plugin-prettier/issues/562 v5 release notes: https://github.com/prettier/eslint-plugin-prettier/releases/tag/v5.0.0