Tailwind 2.0 poor performance as part of a webpack PostCSS build system

Problem

Description of the problem Tailwind CSS 2.0 builds slowly as part of a HMR webpack build system. It is slower than the release, but that could just be due to the amount of CSS generated increasing. I filed a very similar issue a month ago https://github.com/tailwindlabs/tailwindcss/issues/2544 and worked around the problem by splitting the CSS up into separate chunks. Global `@apply` still worked, and everything was great. It's all written up in the article Speeding Up Tailwind CSS Builds However with Tailwind CSS 2.0, the technique described in the article breaks. Desired solution I'm hoping to have the DX of working with Tailwind CSS 2.0 be improved from a HMR build time perspective. I realize that you can only optimize your generation of CSS so much, and a PR is in the works to do just that with `esbuild`. I also realize that part of the slowness here is simply webpack and the surrounding ecosystem being slow when dealing with massive amounts of CSS (though I've optimized that quite a bit here). However, the paradigm that Tailwind CSS is using is what generates a massive amount of CSS, and webpack is a very widely used tool that many things are built upon. Some way to address the DX here would be great; huge gains can be made using the CSS splitting technique described in the article, maybe there could be a way to restore that functionality to Tailwind 2.x? Link to a minimal reproduction: I made a new branch with Tailwind 2.0, webpack 5, PostCSS 8, and all the g