Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
.extract() leads to empty .css files #1914
css files are empty (0 bytes), with no error, whenever a js file has been processed before.
leads to a 0 bytes css file whenever
creates the wanted css.
Steps To Reproduce:
Output in the first case:
and in the second case:
Yeah, saw those - just missed them when trying to upgrade. I took a look at webpack 5 and it appears they are only at 20% :/
Biggest thing my team is missing from 2.x is the new multi-config that you dropped last month so we can do multiple tailwind configurations. Think it's even possible to get it in 2.x?
Well... we have to do not use
There is a note in
I'm having #1889 problem too.
Running into this as well. In my case, we've been using
FWIW, I created a new, clean Laravel / React project and implemented both SASS compiling and code splitting, and things worked just fine. Added in
Update: Looks like
Today I faced the same issue.
So here's a workaround I found.
Next step is to add new scripts into your package.json file
NOTE: On this step, make sure to match that --env.mixfile option with the second webpack file.
I hope it helps.
@vesaka you won't need 2 terminal windows, just