-
-
Notifications
You must be signed in to change notification settings - Fork 9
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 experimental-vite-env-api #85
Conversation
commit: |
@AlemTuzlak If you don't mind quickly testing 🙏 |
Seems to be working correctly in my app - with both, enabled and disabled environment API 😃 |
@pawelblaszczyk5 you're on a mac right? do your asset fingerprints match across client/server? |
Yup, and yup Are you using Tailwind 4 maybe? I've heard that this happens, due to how discovery works with it |
@pawelblaszczyk5 I am, that's the weird thing, it works without this plugin, but doesn't when you add it to the vite config, trying to figure out the root cause atm |
@AlemTuzlak Are you up to date with Tailwind 4? I recall they did some adjustments on their side in one of the recent releases (this/previous week I think) - maybe that's solved on their side? |
@pawelblaszczyk5 that actually fixed it! thanks man, 4.0.9 of tw doesn't cause doubled fingerprinted assets |
This update adds the capability for the plugin to read the React Router future flags.
If
unstable_viteEnvironmentApi
is enabled, then we return a compatible configuration using Vite environments.