-
Notifications
You must be signed in to change notification settings - Fork 291
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
[Remix/Vite] Vanilla generated css files doesn't get injected into html after build #1479
Comments
Thanks for raising an issue. I've reproduced it locally and can confirm that the styles are missing. Specifically, it seem like remix is the side-effect import of the VE file, but it doesn't strip the tailwind one. If I export a style and use it within the app, all styles are present in a stylesheet. I tested this out in a plain vite app and it is not an issue there, so it's specific to remix. |
Okay i'll open an issue on remix instead |
@vincent-thomas Sorry if my response sounded dismissive. I'm happy to keep this issue open at least to provide visibility on the VE side, but an issue in Remix would certainly be useful as well. |
No problem, i totally understand that issues need to be closed and developer time should be focused on real vanilla extract bugs. Maybe this issue could be referenced under this page (https://vanilla-extract.style/documentation/integrations/remix)? NOTE: I can open a pull request regarding this. Btw I really like this library, an issue has been opened remix. |
Tracked in remix remix-run/remix#10045 |
Describe the bug
Vanilla css styles do get injected into html in dev mode, but in production they don't get injected. They do generate in the
build/client/assets
directory but are not 'used'.I use bun as package manager
NOTE: To have exactly my setup use my flake.nix with the nix package manager. not a must at all but its nice.
Head tag in devmode
Head tag in prod
Reproduction
https://github.com/vincent-thomas/remix-vanilla-extract-css-repro
System Info
Used Package Manager
npm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: