Insiders builds content paths not detected

What version of Tailwind CSS are you using? insiders.2a88642

What build tool (or framework if it abstracts the build tool) are you using? Reproduced in two different environments Parcel 2.7.0, postcss 8.4.18

Webpack 4.10.0, postcss 8.4.18

What version of Node.js are you using? v16.14.0

What browser are you using? Chrome

What operating system are you using? Windows 10

Reproduction URL https://github.com/gigsta12/TailwindContentRepro

Describe your issue Using the current versions of insiders e.g. 2a88642 the content paths are not identified when you run the project. None of the css is generated in the output files.

The following is shown in the console.

console: warn - No utility classes were detected in your source files. If this is unexpected, double-check the `content` option in your Tailwind CSS configuration.   

console: warn - https://tailwindcss.com/docs/content-configuration

This has occurred in both in my existing larger webpack project but also in the repro project listed above. Unsure if this is related to the new multiple @config files? Reading the announcement I wasn’t entirely sure if with the upcoming 3.2, the @config is now required to be included in the input css file so I included it anyways.

[thecrypticace]

Thanks for brining this issue to our attention! I figured out the problem and have opened a PR to fix it. We have some other unrelated stuff that’s causing the build to fail which I’ll need to wait for us to fix before merging it.

[thecrypticace]

Of course — thank you for letting us know! ✨

The tl;dr on what happened is that Windows different path separator occasionally requires a bit extra work that otherwise doesn’t need to happen and it was missed in this case.