Enable Tailwind JIT processing #13
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The new JIT feature from Tailwind speeds up tailwind processing by a /lot/, so I've implemented it. This also allows us to reduce the complexity of the css loading pattern a bit, since we no longer need to do the weird thing were we try and convince webpack to handle the parts like separate modules. Unfortunately (as the message when you run it will tell you) JIT is not restrained by semver at this time, so it could change or break at any time. Given that, I'm not going to merge this into main until it hits at lest some kind of stable release. If you want to play around, though, be my guest!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The new JIT feature from Tailwind speeds up tailwind processing by a
/lot/, so I've implemented it. This also allows us to reduce the
complexity of the css loading pattern a bit, since we no longer need to
do the weird thing were we try and convince webpack to handle the parts
like separate modules.
Unfortunately (as the message when you run it will tell you) JIT is not
restrained by semver at this time, so it could change or break at any
time. Given that, I'm not going to merge this into main until it hits at
lest some kind of stable release. If you want to play around, though, be
my guest!