Add configuration option to disable caching. #32
Merged
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.
Caching the compiled CSS makes sense 99% of the time, but I recently ran into a situation where it's better to have it disabled: Using TailwindCSS in JIT mode. Jekyll will recompile the CSS every time any file is changed, but the caching is preventing TailwindCSS from running to actually update the CSS.
An overview of what happens in this case with caching enabled might help explain it better:
Other Changes
I included two other small changes, one is a bug fix for using TailwindCSS and one is a small tweak:
stdin
source inbin/postcss
. This was throwing an error when using TailwindCSS. A workaround is to create anstdin
file in the root, but this seems more sane. This fixes @tailwindcss/jit doesn't work #22. (See 5fa94692).cache_miss
method to help it read a bit better with the cache disabled condition.Let me know if you'd prefer the the
bin/postcss
as a separate PR and I can split them up.