Potential Windows issue

[thomas-noimos]

I'm facing some weird issues on Windows since version 4.0.7. When I was using version 4.0.0, some binaries were not automatically installed. I then installed them and things worked properly (although it was annoying having OS specific libs commited in the package.json). Now, since 4.0.7, I no longer see the crash error that the library is missing, however the styles are not properly generated.

I have my repo cloned exactly the same way via WSL and there everything seems to work smoothly.

Example:
WSL:

Windows:

I'm missing a lot of generated CSS classes there.

What version of Tailwind CSS are you using?

v4.0.15

What build tool (or framework if it abstracts the build tool) are you using?

Vite v6

What version of Node.js are you using?

Tried in 18, 20 and 22

What browser are you using?
Brave
For example: Chrome, Safari, or N/A

What operating system are you using?

For example: macOS, Windows

Reproduction URL

A Tailwind Play link or public GitHub repo that includes a minimal reproduction of the bug. Please do not link to your actual project, what we need instead is a minimal reproduction in a fresh project without any unnecessary code. This means it doesn't matter if your real project is private/confidential, since we want a link to a separate, isolated reproduction anyways.

A reproduction is required when filing an issue — any issue opened without a reproduction will be closed and you'll be asked to create a new issue that includes a reproduction. We're a small team and we can't keep up with the volume of issues we receive if we need to reproduce each issue from scratch ourselves.

Describe your issue

Describe the problem you're seeing, any important steps to reproduce and what behavior you expect instead.

[philipp-spiess]

Hey! Do you mind creating a reproduction for this issue that we can run on our machines?

[thomas-noimos]

For this specific problem it could be hard because I'm using an internal component library. So this library also uses Tailwind V4. Then when consuming the library, that's when I face the issues. Do you think it could be related ?

[thomas-noimos]

Found out the issue. My app wasn't properly setting the @source from the UI Kit library. It was working on other OSes because the package-lock kept some old version of the library installed.