Skip to content
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

Migrate to Prettier v3 #30

Closed
sosukesuzuki opened this issue Oct 19, 2022 · 3 comments · Fixed by #36
Closed

Migrate to Prettier v3 #30

sosukesuzuki opened this issue Oct 19, 2022 · 3 comments · Fixed by #36

Comments

@sosukesuzuki
Copy link

Hi!

The Prettier team is currently working on v3(still alpha).
v3 will include breaking changes to the plugin interface.
Please see https://github.com/prettier/prettier/releases/tag/3.0.0-alpha.2 for more information.

I created this issue to help major plugins migrate to Prettier v3.

Myself and @fisker have created a migration guide which you can see here:

https://github.com/prettier/prettier/wiki/How-to-migrate-my-plugin-to-support-Prettier-v3%3F

If you have any questions, feel free to mention us. We can help you.

If you have already migrated to Prettier v3, sorry but please close this issue.

@kachkaev
Copy link
Member

kachkaev commented Nov 4, 2022

👋 @jwoLondon! Would now be a good time to experiment with Prettier v3? I hope I can produce a version that is compatible with both Prettier v2 and v3, but if this is impossible, when would you recommend me to not release breaking changes?

@jwoLondon
Copy link
Member

Thanks Alex. Yes please, that would be great. If it turns out to create any breaking changes, we can discuss timing via email.

@kachkaev
Copy link
Member

kachkaev commented Nov 5, 2022

It turned out that the existing version (0.8.0) was compatible with Prettier 3 and did not need any changes. I released 0.9.0 with newer dependencies and some internal refactoring anyway. #36 confirms plugin compatibility with Prettier v1, v2 and v3; the repo uses 3.0.0-alpha.4 internally.

User experience should remain the same, I don’t expect any breaking changes except for the dropped Node 12 support (#33).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants