Replies: 3 comments
-
For now I'm including the production build in development via |
Beta Was this translation helpful? Give feedback.
0 replies
-
We have the same problem. |
Beta Was this translation helpful? Give feedback.
0 replies
-
This could be related to this PR/discussion happening - worth keeping an eye on that 👍 |
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.
-
I'm new to tailwind and have been experimenting with it in gatsby and nextjs. I'm including tailwind via postcss using the
@tailwind
directives. I've tested this on tailwind 1.6.3 and 1.7.0 and the performance observed is the same.When I add all three tailwind directives to a css file, incremental development builds in either framework (saving a CSS file in development and waiting for it to re-compile the bundle) goes from taking ~500ms close to 5 seconds.
However, if I remove
@tailwind utilities
, the build times go back to roughly ~500ms.I'm just using the base gatsby and nextjs installs/configs and running the development commands (
gatsby develop
/yarn dev
in next). Using nextjs version 9.5.2 and gatsby version 2.24.41.Has anyone else observed this behavior?
Beta Was this translation helpful? Give feedback.
All reactions