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
tailwindcss started taking 20s to process my repo. I had no idea why, and spent over an hour investigating. It turned out the cause was a temp 3mb html file (generated by rollup-plugin-visualizer).
I think tw should warn if a file takes >3s to be processed. Especially if DEBUG=* is set.
The debug log had no indication as to what file was the reason. All I could learn from it was that tailwindcss_oxide::scanner took 20s from enter to exit.
2025-09-04T12:53:27.647374Z INFO extract_candidates:parse_all_blobs:extract: tailwindcss_oxide::scanner: enter
2025-09-04T12:53:48.172613Z INFO extract_candidates:parse_all_blobs:extract: tailwindcss_oxide::scanner: exit
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
tailwindcss started taking 20s to process my repo. I had no idea why, and spent over an hour investigating. It turned out the cause was a temp 3mb html file (generated by rollup-plugin-visualizer).
I think tw should warn if a file takes >3s to be processed. Especially if
DEBUG=*
is set.The debug log had no indication as to what file was the reason. All I could learn from it was that
tailwindcss_oxide::scanner
took 20s from enter to exit.Beta Was this translation helpful? Give feedback.
All reactions