Migration from v3 to v4 multiplied build time in CI/CD pipeline by 8

[mlarabi]

Hi all,

Facing this "non-issue" but still would like to understand why it is happening.
We have migrated from Tailwind v3 to v4. Moved our internal plugins from tailwind.config.js to CSS and moved from PostCSS to Vite 6 (already used for the SPA app).

Locally everything is smoother, dev environment is faster, and the build goes quickly (less than 1 min).
However on the CI/CD server (Jenkins) it takes 8x more time to complete the build than previously.

I am assuming it has to do with something related to threading during build ? Or something. I am not sure how to tackle that.

Thank you for your support.

[adamwathan]

Is your .gitignore file missing in CI by any chance? That would cause Tailwind to scan tons of extra files.

[mlarabi]

This looks like the right direction. The file does exist, but when building on Docker (on the CD pipeline) with selected files only the build goes back to the normal speed. Thanks for the support, we will investigate what is in the Jenkins workspace that is making Tailwind go through them all.

Any way to apply a flag during build time to see what it is scanning ?

[mlarabi]

Can confirm. After adding some PNPM cache folder in the .gitignore We are back to normal numbers. Thank you for your support.