styled-components
6.6.0 · 12 Oct 2026MIT14.8M / weekRepositoryHomepagenpmAtom feed
Upgrading styled-components From 4.0.2 to 4.4.1
12 releases in betweennotes for 9
Reading releases, release notes and advisories…
- 1+
- change to make
- 0
- advisories fixed
- 9+
- new
- 7+
- fixes
Counted from 9 of 12 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Deprecated4.1.0
Release by release
- Fixed
Fix
styled-components'sreact-nativeimport for React Native Web,
- Fixed
- Fixed
Fix to use
ownerDocumentinstead of globaldocument, - Fixed
Fix attrs not properly taking precedence over props
- Fixed
Fix add check for style tag detached - sheet in the style tag is null in this case,
- Fixed
4.3.1 – 4.3.22 releases, nothing new or fixed in the notes
- New
Add "forwardedAs" prop to allow deeply passing a different "as" prop value to underlying components when using
styled()as a higher-order component (see #2580) - New
Implement defaultProps folding (see #2597)
- Fixed
Fix components being folded inappropriately when an interim HOC is present (see #2586)
- Fixed
Fix
themeprop for styled native components, also fixesthemeindefaultPropsfor them (see #2576)
- New
4.2.1no release note
- New
Add svg tag
markerto domElements.js (see #2389) - New
Expose
StyleSheetContextandStyleSheetConsumerfor you fancy babes doing wild stuff - Fixed
Fix an edge case where React would break streaming inside
<textarea>elements, which have special child behavior and aren't a suitable place to inject a style tag (see #2413)
- New
4.1.1 – 4.1.33 releases, nothing new or fixed; 2 without a note
- Deprecated
Attrs can now be passed a function (see #2200); thanks @oliverlaz for providing an early PoC PR for this!
- New
Allow disabling "speedy" mode via global
SC_DISABLE_SPEEDYvariable, - New
Add pixels to unitless numbers when object interpolation is used,
- Deprecated
15 other lines we could not sort, mostly version bumps
- 4.4.1
Remove dev-time warning if referencing a theme prop without an outer
ThemeProvider, the check for it isn't smart enough to handle cases with "or" or ternary fallbacks and creates undesirable noise in various third party integrations - 4.4.0
Backport fix for SSR classname mismatches in development mode for some environments like next.js (see #2701)
- 4.4.0
Backport fix where classnames are composed in the wrong order if custom class names are passed in (see #2760)
- 4.3.1
Revert #2586; breaks rehydration in dev for certain runtimes like next.js
- 4.3.0
Make it possible to initialize
SC_ATTRandSC_DISABLE_SPEEDYviaREACT_APP_*.env variables for easier integration with CRA applications (see #2501) - 4.2.0
Reduced GC pressure when using component selector styles. (see #2424).
- 4.2.0
Make the
GlobalStyleComponentcreated bycreateGlobalStylecall the base constructor withprops(see #2321). - 4.2.0
Move to Mono repository structure with lerna @imbhargav5 (see #2326)
- 4.2.0
- 4.1.1
Put back the try/catch guard around a part of the flattener that sometimes receives undetectable SFCs (fixes an errant hard error in an edge case)
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.