I am having similar issues to the ones that have been raised before, prettier-vscode does not seem to respect my project's .prettierrc.json configuration when formatting HTML files. The print width seems to be defaulted to 80 instead of our custom value of 100.
{
"printWidth": 100,
"tabWidth": 4,
"singleQuote": true
}
My vscode is setup to format on save, and our project's package.json references "prettier": "1.15.2".
The extension is up to date in vscode too.
Our project does not have a print width setting in the .editorconfig file either.
I created a video reproduction of the issue where I save an AngularJS template file in vscode and it gets wrongly re-formated, and then apply the Prettier CLI on that file which puts it back to its correct format.
The video is available here (Dropbox - 2.1 MB).
Can you share the repo shown in your video? (Not private)
Can you debug it?
I created the following repository with one html file that reproduces the issue: vscode-prettier-bug.zip

I wanna use default vscode formatter for html. I guess perviously prettier doesn't have html formatter, but in 1.7.2, prettier tries to format html, so it doesn't respect vscode default html formatter. I also tried to set "prettier.disableLanguages": ["html"], but this disables default vscode formatter as well.
same problem, install 1.6.1, it works .(this problem happened since ver1.7.0+ )
Also you can disable html in settings,"prettier.disableLanguages": ["html"] @wghglory .
It seems we do not infer the same parser as prettier's cli.
This extension uses angular parser where prettier uses html parser.
CLI:
The extension doesn't take into account files' extensions, only vscode's languageId
To workaround this issue. You can specify explicitly the parser you want to use.
In my case, another extension was causing this issue. I uninstalled "XML Tools" and it started working!
VS Code now prompts you to select which formatter to use when you have multiple on the same file type.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Most helpful comment
It seems we do not infer the same parser as prettier's cli.
This extension uses angular parser where prettier uses html parser.
CLI:
Extension:
The extension doesn't take into account files' extensions, only vscode's languageId
To workaround this issue. You can specify explicitly the parser you want to use.