-
Notifications
You must be signed in to change notification settings - Fork 15
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
Support Vite 5.0 #22
Comments
Absolutely! We're working on an upgrade but are blocked by some backwards compatibility issues between the Vite 4.0 and 5.0 Plugin TS type. The Plugin type has changed substantially and means that although this plugin works in a backwards compatible way, we get a type error thrown in the We can deprecate previous versions of Vite, but it's likely for people on large projects which are on <5.0 (say, on |
How about bumping the major version on |
I saw that someone started publicly working on this as #24 - is there anything else that would help get vite 5 support soon? |
I don't mean to bother you, but did you have a chance to look closer at this, @tonyketcham? Or do you have an idea of when you might get around to it? I understand if working on this isn't your priority right now, I'm just asking so I can plan around it myself. If you don't have the capacity to work on this right now, that's perfectly fine! |
Apologies for the lengthy delay, totally my fault! I'm planning on having this sorted by the end of this week with a release :) |
This has been shipped in v1.1.0! 🎉 |
Hi,
First of all thank you for this super easy-to-use plugin. It has been a joy to use it without any issues and it empowers builds of privacy.sexy.
Vite 5 is released and this package requires maximum of Vite 4.x as peer-dependency.
Can we update it to support Vite 5 so it does not block users' migration?
The text was updated successfully, but these errors were encountered: