You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before I open a pull request, I wanted to confirm that functionality is now slightly different from the current README.
I upgraded prettier to v3 and was getting the error: [error] No parser could be inferred for file "/path/to/xml/file.xml".
I was able to fix this by adding the following plugin section to my .prettierrc file:
"plugins": ["@prettier/plugin-xml"]
This wasn't entirely obvious anywhere in the documentation either here or in the main prettier repo. I think it would be useful to mention here now that plugin search has been disabled in prettier v3?
The text was updated successfully, but these errors were encountered:
Strings provided to plugins are ultimately passed to import() expression, so you can provide a module/package name, a path, or anything else import() takes.
I tried a few things unsuccessfully (plugin-xml, prettier-plugin-xml) before using the full npm package name (@prettier/plugin-xml). The README here implied it should "just work", which threw me off a little longer. I'll open a PR asap. Thanks.
Before I open a pull request, I wanted to confirm that functionality is now slightly different from the current README.
I upgraded prettier to v3 and was getting the error:
[error] No parser could be inferred for file "/path/to/xml/file.xml".
I was able to fix this by adding the following plugin section to my
.prettierrc
file:This wasn't entirely obvious anywhere in the documentation either here or in the main prettier repo. I think it would be useful to mention here now that plugin search has been disabled in prettier v3?
The text was updated successfully, but these errors were encountered: