fix(builder): add explicit source() path for consistent Docker builds #291
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, etc.) in production/staging Docker builds.
Problem
After migrating UI packages to npm, the sidebar layout was broken on staging because Tailwind wasn't generating responsive classes from the
@openzeppelinnpm packages. The@sourcedirective was correctly pointing to node_modules, but path resolution differed between local development and Docker builds.Solution
Add explicit
source()function to set the Tailwind base path to the monorepo root:This ensures consistent path resolution in both local dev and Docker builds, allowing the
@sourcedirective to correctly scan npm packages for class names.Testing
xl:block,xl:flex,xl:flex-col,xl:hiddenclasses