Packages

styled-components

6.6.0 · 12 Oct 2026MIT14.8M / weekRepositoryHomepagenpmAtom feed

Upgrading styled-components From 4.2.1 to 4.4.1

5 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 4.2.1Latest6.6.0
0
changes to make
0
advisories fixed
2
new
6
fixes

Release by release

  1. 4.4.1

    30 Oct 20191 fix
    • Fixed

      Fix styled-components's react-native import for React Native Web,

  2. 4.4.0

    23 Sep 20193 fixes
    • Fixed

      Fix to use ownerDocument instead of global document,

    • 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,

  3. 4.3.1 – 4.3.22 releases, nothing new or fixed in the notes

  4. 4.3.0

    5 Jun 20192 new · 2 fixes
    • 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 theme prop for styled native components, also fixes theme in defaultProps for them (see #2576)

5 other lines we could not sort, mostly version bumps
  • 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.1
  • 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.4.0
  • Revert #2586; breaks rehydration in dev for certain runtimes like next.js

    4.3.1
  • Make it possible to initialize SC_ATTR and SC_DISABLE_SPEEDY via REACT_APP_* .env variables for easier integration with CRA applications (see #2501)

    4.3.0

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.