Fix CSS being tree-shaken in production builds by declaring styles.css as#961
Merged
ted-palmer merged 2 commits intomainfrom Mar 5, 2026
Merged
Fix CSS being tree-shaken in production builds by declaring styles.css as#961ted-palmer merged 2 commits intomainfrom
ted-palmer merged 2 commits intomainfrom
Conversation
…sideEffect After migrating from Panda CSS to Tailwind, the external styles.css file was being dropped by bundlers in production due to "sideEffects": false. This marks all CSS output paths as side effects so bundlers preserve them. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
pedromcunha
approved these changes
Mar 5, 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
2 participants
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.
No description provided.