-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot read properties of undefined (reading 'parsers') #49
Comments
👋 @kantuni! Which version of Prettier are you using? Can you please provide reproduction steps? For the plugin to work in VS Code, it is necessary to list it in the Prettier’s config file: https://prettier.io/docs/en/plugins.html. E.g. in {
"plugins": ["prettier-plugin-foo"]
} |
Could it be related to the problems with Prettier in vsCode since V9.16? |
Prettier 3.0 has dropped support for automatic plugin search because it had a lot of hard-to-solve issues (prettier/prettier#14759). Prettier plugins are is usually installed locally and are declared in Prettier config file. This file is located at the root of the project folder. How difficult would be to change our recommended setup flow to a local copy of Prettier? If we cannot do that, we can stick with Prettier v2 or ask editor maintainers to support global plugins somehow. |
I updated instructions for now: 56c32ae. @jwoLondon feel free to improve them if you see any opportunities. |
The issue was caused by Prettier v3. After downgrading to v2, everything works smoothly. |
Hmm, that’s odd. What was the context in which your were getting this error? This repo runs tests against Prettier v1, v2 and v3, so I it’d be great if you could help with the reproduction. If anyone else experiences issues with |
Hey @kachkaev 👋 , Sorry for a late response. I just saw this message. I'm trying to setup Happy to help repro! |
I get
when I run
P.S. I can't get it to work in the VSCode either.
The text was updated successfully, but these errors were encountered: