Prettier does not consistently respect .prettierrc, .eslintrc nor vscode settings

There are several issues in this repo regarding inconsistent behavior from this extension, so maybe this issue is already posted, but I couldn’t know for sure.

I have a .prettierrc file, a .eslintrc file and even vscode settings with the same 80 print-width settings, but the extension just doesn’t respect it. It does try to format the line, but not enough (and not like the prettier.io playground).

It has worked in the past, but not today, maybe it is an update, I don’t know. I’ve disabled auto-update from now on.

Is there any way to debug this extension? I don’t know whether it ever works and respects all my rules or if it just making things up. It’d be great if I could see what rules prettier is inferring from my setup in every file.

For example:

• someFile.js => “Check inferred prettier settings for this file”
  • printWidth: 70 (from /.prettierrc)
  • tabWidth: 4 (from vscode settings)
  • singleQuote: true (from global prettier config)

I don’t know if my config is messed up, or if there is a bug in the extension, or if there is a bug in vscode or if I should restart my machine (I tried).

[aztack]

.prettierrc.js is a valid config name in Prettier, but it does not work with the VSCode extension here.

.prettierrc.json works. prettierrc.js and prettierrc.config.js do not work.

[arrygoo]

I’ve been having this issue since a few days ago and disabling the chrome debugger plugin didn’t fix it for me. So frustrating as I want to stick with VSCode, but eslint/prettier integration seems to have broken