You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes the tailwind jit engine breaks in dev mode and new styles added is not reflected in the application. See related issue in: tailwindlabs/tailwindcss#4081
Possible solutions
As a temporary patch, try modifying the tailwind config file or deleting the .next folder and restart the dev server
If you are looking for a more permanent fix, downgrading to webpack v4 supposedly helps. In next.config.js:
future: {
webpack5: false,
},
Another fix would be to opt-out of jit mode, by deleting this line in tailwind.config.js
We will update to the newest version of tailwind css when the problem is fixed, but otherwise, there are no further plans to update the template for now.
The text was updated successfully, but these errors were encountered:
To clarify, none of those fixes worked for me, but removing the line `mode:
"jit"` from `tailwind.config.js` then saving and adding it back does seem
to work fine, without needing to restart the dev server.
Downgrading to webpack 4 reduces the frequency that JIT stops working but
doesn't eliminate it.
The issue basically isn't being tracked over in TailwindCSS because no one
can reliably reproduce it, though it seems to be affecting everyone using
Next, so it does get re-reported every few days.
Thanks for opening the issue to clarify Tim
Problem
Sometimes the tailwind jit engine breaks in dev mode and new styles added is not reflected in the application. See related issue in: tailwindlabs/tailwindcss#4081
Possible solutions
.next
folder and restart the dev servernext.config.js
:tailwind.config.js
We will update to the newest version of tailwind css when the problem is fixed, but otherwise, there are no further plans to update the template for now.
The text was updated successfully, but these errors were encountered: