-
Notifications
You must be signed in to change notification settings - Fork 4.5k
[v4] Tailwind running with Next v15 on Docker takes ton of time and resources for first load #15882
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hey! My guess is that |
I inspected the running container using However, the problem persists, but it's not as bad as I thought. |
I've tried running your repro on my machine but somehow can't connect to the dev server started inside the container. Are you doing anything other than I'm curious if you have looked at full-build times too and if this issue only appears when you add the Tailwind CSS postcss plugin? |
What version of Tailwind CSS are you using?
v4.0.0
What build tool (or framework if it abstracts the build tool) are you using?
Next.js v15.1.4
What version of Node.js are you using?
v23.0.0
What browser are you using?
N/A
What operating system are you using?
MacOS
Reproduction URL
I have an issue running Next v15 + Tailwind v4 on a Docker container: the first compiling takes a huge amount of time compared to running
yarn dev
on local. Furthermore, it takes a ton of CPU and memory just for the first rendering.Local

yarn dev
Docker container

docker stats
The text was updated successfully, but these errors were encountered: