AFAIK this is intentional as a performance trick so it doesn’t have to recompute classes all the time.
Since you should be rebuilding your CSS on release, you don’t get any of the “dead” classes in production since it will start from a clean state.
soup
informatom
I can confirm, that updating to tailwind 2.1 resolves the issue even with webpack v4. Thanks!
1
bobkocisko
Thank you everyone for this helpful discussion! Just to add my experience: Even with Tailwind 2.1 I still need to comment out .concat(devMode ? [new HardSourceWebpackPlugin()] : []) in webpack.config.js or else everything is unpredictable.
1