fix(core): restore Tailwind theme bridge from styles export#358
Merged
Conversation
commit: |
interacsean
approved these changes
Jul 3, 2026
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.
Motivation
A regression reported in discussion #311 showed that consumer-authored Tailwind utilities such as
bg-card,border-border, andtext-muted-foregroundstopped resolving after@tailor-platform/app-shell/theme.csswas turned into a no-op compatibility shim.The tricky part is that we now have consumers in both states: some still import
theme.css, while others removed it after the shim release. We need to restore the Tailwind v4 theme bridge for both groups without makingtheme.cssmeaningful again.Design Decision
Keep the public
@tailor-platform/app-shell/theme.cssexport as the current no-op compatibility shim, and instead make@tailor-platform/app-shell/stylesthe single real entrypoint for consumer styling.To do that, this PR turns
stylesinto a thin raw CSS wrapper that imports:The precompiled stylesheet is renamed to
app-shell-core.csssoapp-shell.csscan become that wrapper. This preserves compatibility for apps that either kept or removed the legacytheme.cssimport.Summary
app-shell.csswrapper and sharedtheme.bridge.cssbridge sourceapp-shell-core.cssand keep the internal build pointed at the shared bridge