Repository navigation
Version Packages - #428
Merged
Merged
Version Packages#428
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
October 22, 2026 22:24
0febd87 to
e012896
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 22, 2026 22:24
e012896 to
c4db5bb
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.3.1
Patch Changes
cssprop is used in a CommonJS file without astyled-componentsimport.cssprops.minmax(\n 0,\n 1fr\n); // comment). The comment check required balanced parentheses on the line, so the unmatched)made the comment look like it was inside a value; after lines were joined, styled-components treated everything after//as a comment and silently dropped the following declarations and nested blocks. Unmatched closing parentheses are now ignored, which also stopsurl(//...)values after them from being truncated.declare moduleblock also importsstyled-components.import typefromstyled-componentswhen finding the realstyledimport.styled.default.xlosing displayName and componentId withimport * as styledalongside the css prop or a default import.styledin a named import are recognized now. Inimport { css, styled } from 'styled-components',cssandkeyframesare minified, and with pure annotations turned on they are marked pure.styled.default(Component)withimport * as styledorrequire.styledunder any local name, such asimport { styled as sc }orconst sc = require('styled-components').styled.box,styled.foo, andstyled.feNotAFilterare real components.const styled = require('styled-components'),import sc from 'styled-components',sc.default,ns.default, and__importDefault(require('styled-components')).defaultare that factory. Known non-tag exports stay plain, includingsc.css,sc.keyframes,sc.createGlobalStyle,sc['createGlobalStyle'],sc.isStyledComponent, andsc.default.css. Names onObject.prototypeorFunction.prototypestay plain too, includingsc.hasOwnProperty,sc.toString,sc.bind,sc.__lookupGetter__,sc.name, andsc.__proto__. A computed key is resolved when it is a string, a template whose parts all fold to strings, or a const initialized to one of those, soconst name = 'css'; sc[name],sc[`css`], andsc[`${'css'}`]stay plain, whileconst css = 'div'; sc[css]andsc.default[css]keep their ids. A key this plugin cannot resolve stays plain onrequire()and on an alias that is not namedstyled, solet dynamic = 'css'; sc[dynamic]returns the helper instead of throwing.styled[dynamic]on an import namedstyledis still decorated. Aletorvarthat starts as the factory keeps its display name on a straight-line use written before the reassignment. A use inside a nested function, or inside a loop that also reassigns the binding, is left alone, so that function and the next loop iteration do not throw.content: "it's"; // note).