Replies: 1 comment
-
Update
I am now seeing a new error, some progress 🤔
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Current architecture for v3 Tailwind
postcss.config.js
,tailwind.config.js
andvite.config.mts
config filesv4 upgrade steps
I am seeing NO errors whatsoever, both compilation and runtime. It all seems to be failing silently. My local dev environment runs fine but my app is now completely unstyled. The browser is not loading any tailwind related CSS at all it seems.
upgrade
tool but it didn't appear to find mybase.scss
and simply upgrade the dependencies. The only changes added were inpackage.json
tailwindcss/vite
in myapp/css/vite.config.mts
(we have an entire microfrontend for serving our monolithic CSS for dev, for hot reload reasons)postcss
entirelytailwind.config.js
and use@theme
inside mybase.scss
(I also tried the@config '../tailwind.config.js
approach)@import 'tailwindcss' source('../../*')
and multiple@source
declarations all mimicking what was in mycontent: []
in the old tailwind JS config. Still no luck@import 'tailwindcss'
module could not be found. Not entirely sure what that tells me apart from the obvious.I have read hours worth of issues and discussions on this topic and feel like I have exhausted my options. My conclusion is that my particular setup is still expecting a CSS in JS pipeline and that v4 has changed their philosophy in bringing everything back to CSS first (which I do like FYI).
I am sure you can appreciate this would be very difficult to replicate in a repo, so I hope I have given enough context and someone in a similar situation has some lessons learned or tips. Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions