Open aymanoid opened 4 days ago
Hello,
It’s fascinating to see how tools like Tailwind CSS and Next.js adapt to rapid ecosystem changes, but it's equally a reminder of how tricky cross-platform compatibility can be—especially when Windows gets thrown into the mix. The fact that the app still runs fine is a testament to how resilient these modern frameworks are, even when they're yelling warnings at us. It's like driving with the "check engine" light on but still enjoying the ride! That said, diving into verbose mode or waiting for the este enlace Tailwind team to iron out these quirks might save you some future headaches. It’s also a reminder to always keep an LTS version of Node.js handy
What version of Tailwind CSS are you using?
@tailwindcss/postcss@4.0.0-beta.2 tailwindcss@4.0.0-beta.2
What build tool (or framework if it abstracts the build tool) are you using?
https://tailwindcss.com/docs/v4-beta#upgrading-from-v3 Next.js 15.0.3
What version of Node.js are you using?
v22.11.0
What operating system are you using?
Windows 11
Reproduction URL
Just a fresh project initiated with
pnpx create-next-app@latest
, thenpnpx @tailwindcss/upgrade@next
was used to upgrade to v4Describe your issue
I keep getting this warning that seems to be related to webpack whenever I run dev or build command. I'm guessing it's something related to Windows' weird pathing, but not sure. The application seems to work fine though.