Repository navigation
Version Packages - #433
Merged
Merged
Version Packages#433
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 3, 2026 04:30
91d5f26 to
3be321d
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
babel-plugin-styled-components@2.4.0
Minor Changes
@babel/core@8without peer dependency warnings or errors, and thecssprop transform no longer crashes witht.jSXIdentifier is not a functionon Babel 8. The plugin also no longer depends on@babel/plugin-syntax-jsx, which only accepted Babel 7 as a peer.Patch Changes
cssprop now works on custom elements like<my-foo-bar>and<foo-1>, on lowercase names with no variable of that name in scope like<clipPath>and<foo_bar>, and on hyphenated members like<Icons.arrow-up>. These used to compile to code that referenced a variable that doesn't exist, likestyled(clipPath), and threw when it ran. A lowercase name that does match a variable, like<myButton css>afterconst myButton = styled.button, still styles that variable.ReferenceError: Cannot access 'x' before initializationwhen thecssprop is used on a component declared in the same file (such asconst { Paragraph } = Typography) and the css reads aconstdeclared further down; the generated component now follows every value its css reads.