Repository navigation
Fix Tailwind not generating any utilities - #101
Merged
Merged
Conversation
This file contains hidden or 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
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.
After the Tailwind CSS 4 migration in #98, the deployed
main.cssonly contains the theme and preflight, with no utility classes, so the whole layout of https://flame-engine.org is broken.Cause
jekyll-postcss runs PostCSS with
from: undefined. Without a file path,@tailwindcss/postcssresolves@sourcepaths relative to itsbaseoption, which defaults to the current working directory (the repository root). The@source "../../_includes/**/*.html"style paths were written relative toassets/css/, so they pointed outside of the repository and nothing was scanned.Fix
@sourcepaths inassets/css/main.cssare now relative to the repository root.postcss.config.jspassesbase: __dirname, so the result does not depend on the working directory.Compiled the same way jekyll-postcss does it, the CSS goes from 7.5 KB (identical to the deployed file) back to 17 KB, and the generated classes match the Tailwind CSS 3 output from before #98, plus the dino game classes.