Replies: 1 comment 1 reply
-
Hi, |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying to guess what makes tailwind watch so slow.
My build normally takes >=500ms to update after re-saving a file without changes.
Here is how it normally looks like:
I have 117 files matching the config:
My expectation was that a tiny change (which most changes are) should compile fast due to in-memory cache of unchanged files content.
Am I wrong about it? Should I expect a linear grow of
watch
performance with the number of files in the project?Beta Was this translation helpful? Give feedback.
All reactions