-
Notifications
You must be signed in to change notification settings - Fork 26
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
Stopped working in version 3.2.0 #108
Comments
Hi @tuzz, I'm sorry that is stopped working for you. Have you tried to exclude one plugin at time to see if something interferes with my plugin? What is changed basically is the removed support for the old vite plugin legacy behavior. Maybe in your case the bug I removed instead is a feature for you. I will check with your project to help you solve this problem and propose a fix or something else. This week I'm busy, you can use the old version in the meanwhile. Of course we will solve this problem asap |
Hi @tuzz thank you for the issue. Essentially the problem was that the code that I deleted had the purpose to support the official legacy plugin. Since the official legacy plugin of Vite now inject the CSS code for other reasons I deleted that code from my plugin. See you! |
Thanks for the fix! Greatly appreciated. ⭐ |
@marco-prontera JIT (just in time) in its all glory! 👍 Just in time because today I noticed that UMD entry doesn't contain css injections. #youcool |
vite build --watch |
Hello, I tried to upgrade to version 3.2.0 but the plugin seems to have stopped work. It is not placing the inlined CSS into the JavaScript umd.js generated as part of my Vite build process. It looks like these two changes were made in this version:
Do you know what could have caused the plugin to stop working?
I am the maintainer of https://github.com/beyondWords-io/player and when I run
./bin/build
it produces adist/umd.js
that is around 375KB and when I upgrade the plugin and run./bin/build
it produces adist/umd.js
that is around 185KB.Thanks
The text was updated successfully, but these errors were encountered: