Cannot read properties of undefined (reading 'parsers') about prettier-plugin-elm HOT 7 OPEN

I updated instructions for now: 56c32ae.

@jwoLondon feel free to improve them if you see any opportunities.

from prettier-plugin-elm.

👋 @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 .prettierrc.json:

{
  "plugins": ["prettier-plugin-foo"]
}

from prettier-plugin-elm.

Could it be related to the problems with Prettier in vsCode since V9.16?

prettier/prettier-vscode#3045

from prettier-plugin-elm.

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.

from prettier-plugin-elm.

The issue was caused by Prettier v3. After downgrading to v2, everything works smoothly.
Thank you!

from prettier-plugin-elm.

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 prettier-plugin-elm after upgrading to Prettier v3, please give us a shout and we will reopen this issue!

from prettier-plugin-elm.

Hey @kachkaev 👋 ,

Sorry for a late response. I just saw this message.

I'm trying to setup prettier-plugin-elm with prettier-plugin-tailwindcss (which requires Prettier v3).
But no matter what I do, VS Code refuses to show Prettier as a formatter for Elm files.

Happy to help repro!

from prettier-plugin-elm.