[error] Couldn't resolve parser "sh". when upgrading to Prettier 3.1.0

[nbouvrette]

I just upgraded to Prettier 3.1.0 this morning and got this new error:

[error] Couldn't resolve parser "sh".

When I downgrade to Prettier 3.0.3 the problem dissapears.

How to reproduce:

1. Clone https://github.com/Avansai/next-multilingual
2. Edit packages.json and set Prettier to version 3.1.0
3. run npm install
4. run npm test

[JounQin]

Seems like a prettier core bug?

cc @fisker @sosukesuzuki

[fisker]

I'll take a look.

[fisker]

Not bug. Missed plugins https://github.com/Avansai/next-multilingual/blob/main/example/.prettierrc.yaml

[fisker]

$ npx prettier --find-config-pah example/.env.development
example/.prettierrc.yaml

[JounQin]

I just upgraded to Prettier 3.1.0 this morning and got this new error:

When I downgrade to Prettier 3.0.3 the problem dissapears.

@fisker But it seems a regression, what means config resolution changed.

[fisker]

Maybe a bug was fixed accidentally.

[fisker]

Oh, caused by prettier/prettier#15433, in pre-v3.1 we doesn't format that file at all.

https://github.com/Avansai/next-multilingual/blob/c48503df8062304e215919a9ea2f04476d9b253a/package.json#L109C18-L109C36

[fisker]

And that's a bug you rasied.. prettier/prettier#15079 😄

[JounQin]

OK, last thing is that the error message is a bit confusing? It successfully understands that it should use sh as the parser what means prettier-plugin-sh is already loaded correctly.

[fisker]

No, the plugin is not loaded, the config file tells prettier to use that parser, https://github.com/Avansai/next-multilingual/blob/c48503df8062304e215919a9ea2f04476d9b253a/example/.prettierrc.yaml#L25

[JounQin]

Hah, that makes sense then! Thanks for your explanation! Close due to answered as above then.

[nbouvrette]

Thanks @fisker and @JounQin - I'm not sure why it was working before?

I thought there was some sort of inheritance but maybe this is gone? in any case adding the plugins section in the example prettier config seems to solve the issue.

[JounQin]

I'm not sure why it was working before?

Oh, caused by prettier/prettier#15433, in pre-v3.1 we doesn't format that file at all.

Please read the conversation carefully.

[nbouvrette]

I think I get it - thanks for looking into this!