fix(builder): explicitly list npm packages for Tailwind scanning #293
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
The previous @source directive pointed to node_modules/@OpenZeppelin which contains symlinks to .pnpm directory. Tailwind v4 doesn't follow these symlinks properly when scanning for class names. This fix explicitly lists each npm package that contains Tailwind classes: - @openzeppelin/ui-components - @openzeppelin/ui-renderer - @openzeppelin/ui-react This ensures responsive classes like xl:hidden, xl:flex, etc. are properly detected and included in the final CSS output.
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.
Summary
Fix missing responsive Tailwind CSS classes (
xl:hidden,xl:flex,xl:block,xl:flex-col) in production builds after the UI kit extraction to npm packages.Problem
After migrating UI packages to npm, the sidebar layout was broken on staging because Tailwind wasn't generating responsive classes. The root cause:
node_modules/@openzeppelin/ui-components→.pnpm/@openzeppelin+ui-components@1.0.1.../@source "../../../node_modules/@openzeppelin"directive scanned a directory containing symlinksSolution
Explicitly list each npm package that contains Tailwind classes:
When specifying a path directly to a symlink (rather than its parent directory), the filesystem resolver follows it to the actual location containing the source files.
Testing
xl:block,xl:flex,xl:flex-col,xl:hiddenclasses