Skip to content

Process tailwind features together #520

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 16, 2018

Conversation

adamwathan
Copy link
Member

Resolves #519.

The way Webpack runs PostCSS stuff is a little hard to fully understand — some stuff seems to run only once, some stuff runs every time a build happens, etc.

As part of a refactoring in an earlier commit, I tried to extract all of Tailwind's processing to it's own plugin so I could stop passing around lazyConfig everywhere and still have changes to tailwind.js be respected on watch, but apparently I wasn't properly testing that it was still working because I broke it 🙃

After some googling and trial and error, I figured out I can wrap all of these plugins in another plugin that runs all of the plugins synchronously, and this will cause Webpack to properly respect changes to the config file. Fingers crossed there are no unwanted side effects here, but I think we'll have to just throw it into the wild to know for sure.

@adamwathan adamwathan merged commit 37493ed into master Jul 16, 2018
@adamwathan adamwathan mentioned this pull request Sep 14, 2018
@adamwathan adamwathan deleted the process-tailwind-features-together branch January 21, 2019 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant