Try Version 12

[ntotten]

We have released a major update to the Prettier VS Code extension and are moving to the Prettier VS Code org. Try the new BETA version of the extension here and open any issues if you find problems.

https://marketplace.visualstudio.com/items?itemName=Prettier.prettier-vscode

The current version on the old org is still the latest stable release.

[HummingMind]

Are you guys going to also publish v12 (prettier.prettier-vscode) for Cursor (in Open VSX registry)? Or not yet?

[ntotten]

Are you guys going to also publish v12 (prettier.prettier-vscode) for Cursor (in Open VSX registry)? Or not yet?

#3832

[tats-u]

When are you going to deprecate the previous esbenp.*? It is confusing that the previous one shows at the top of the search result in VS Code. The README of the previous one should have recommendations for the new one (prettier.*). I found one but it is not that noticeable. The plugin name and README title should add a suffix like "(old)" or "(Legacy)".

[coliff]

When are you going to deprecate the previous esbenp.*? It is confusing that the previous one shows at the top of the search result in VS Code. The README of the previous one should have recommendations for the new one (prettier.*). I found one but it is not that noticeable. The plugin name and README title should add a suffix like "(old)" or "(Legacy)".

It does explain on the README already

🚨 Extension Migration: This extension is being moved from esbenp.prettier-vscode to prettier.prettier-vscode. Version 12+ is only published to the new for now as it is a major change. Once it is stable, we will publish v12 to both extensions and deprecate the esbenp.prettier-vscode extension. Version 12.x is currently not stable, use with caution and report bugs.

[ST-DDT]

There is also a deprecation workflow that you can use to migrate all users to the new plugin id:

https://code.visualstudio.com/api/working-with-extensions/publishing-extension#deprecating-extensions

Especially the last part of that.

[tats-u]

It does explain on the README already

It must be placed higher up.

[tats-u]

Why did you downvote? No warning appears at the first display:

It is not sufficient. It is too low.

[coliff]

Because the new version is intentionally not promoted because the new version isn't stable yet - it's still in testing.

Once it's ready it will be much more visible and the old extension have a deprecated warning, like the old HTMLHint one does. But it makes sense not to do that until the new version is ready and stable - and available on Open VSX so that users of Cursor can use it. :-)

[tats-u]

If so I think that you can add a red-background "Preview" label at the right to the package name. Have you not seen ones in other extensions?

[coliff]

If so I think that you can add a red-background "Preview" label at the right to the package name. Have you not seen ones in other extensions?

Yes, I agree that could be a good idea :-)