Skip to content

fix(styled-jsx): Fix specificity issue by parsing twice #464

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 9 commits into from
May 28, 2025
Merged

Conversation

kdy1
Copy link
Member

@kdy1 kdy1 commented May 28, 2025

No description provided.

@kdy1 kdy1 self-assigned this May 28, 2025
Copy link

changeset-bot bot commented May 28, 2025

⚠️ No Changeset found

Latest commit: 94f522f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@kdy1 kdy1 enabled auto-merge (squash) May 28, 2025 17:04
@kdy1 kdy1 merged commit 8dd3e22 into main May 28, 2025
9 checks passed
@kdy1 kdy1 deleted the kdy1/styled-jsx branch May 28, 2025 17:08
kdy1 added a commit to vercel/next.js that referenced this pull request May 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant