Tailwind classes awkwardly purging in development

[tonyketcham]

Describe the bug

Adding a new Tailwind class during development doesn't reliably cause the browser to hot drop in the style, leaving you to have to do an Empty Cache and Hard Reload in the browser to see it.

Running yarn static builds & exports the site then pops open a local server of the build, which shows the Tailwind classes being correctly included.

Expected behavior

Adding a Tailwind class to your project should automatically reflect it in the browser the first time it's used in your project without any tomfoolery. Tailwind should probably just throw up all the classes into the global.css while in Dev and only purge in Production. It's currently configured that way but there must be something conflicting.

[tonyketcham]

Fixed in 6ae840a