Packages

styled-components

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

Upgrading styled-components From 6.5.0 to 6.6.0

4 releases in betweenevery note read

Reading releases, release notes and advisories…

0
changes to make
0
advisories fixed
2
new
18
fixes

Release by release

  1. 6.6.0

    12 Oct 20262 new · 11 fixes
    • New

      Added a StyledComponent<Target, Props> type for annotating explicitly-typed styled component exports.

    • New

      Added a development-only warning for when the server and the browser are running different versions of styled-components. Class names are derived in part from the library's own version, so a mismatch made every server-rendered class name silently fail to match on the client, with no hint as to why styles disappeared or hydration broke. The warning names both versions and points at npm ls styled-components to find the duplicate. A page that intentionally hosts more than one app, each on its own styled-components version (for example a micro-frontend setup), can ignore it. It is stripped from production builds.

    • Fixed

      Fixed attrs no longer applying its value when a prop was explicitly passed as undefined (the 6.3.12 to 6.5.x behavior). styled.button.attrs(({ type = 'button', ...rest }) => ({ type, ...rest })) rendered without type="button" when the caller passed type={undefined}, and an object-form default such as .attrs({ type: 'button' }) was lost the same way, including through a wrapper component that spreads its own props over the styled component. attrs now always wins for the keys it returns, matching every other case where a prop is passed alongside attrs.

    • Fixed

      Rendering styled-components on the server with the edge runtime (for example export const runtime = 'edge' in a Next.js route) now fails with a clear message that names the fix: use the Node.js runtime for routes that render styled-components. Previously the same setup ended in an obscure crash, either at next build or on the first request.

  2. 6.5.3

    15 Aug 20261 fix
    • Fixed

      Fix TypeScript errors in projects that augment React HTML props with a data-* template-literal index signature.

  3. 6.5.2

    11 Aug 20263 fixes
    • Fixed

      .attrs() is cheaper to type-check.

    • Fixed

      Explicitly annotated styled components type-check faster.

    • Fixed

      styled() wrapping a generic polymorphic component keeps its declared props narrow.

  4. 6.5.1

    7 Aug 20263 fixes
    • Fixed

      Fix a styled component silently dropping props declared as a union whose members have no prop in common, which left every one of those props rejected. The same applied when as pointed at a component with such props. Where every member's props are optional the union is still flattened, so declare the combined optional shape instead.

    • Fixed

      Styled components now report the same debug value to React DevTools on every render. Previously the value was only reported on renders that recomputed styles, so it disappeared from the DevTools panel whenever a component re-rendered with unchanged style props.

    • Fixed

      Fix wrapping a component whose props are a union. Since 6.5.0 the wrapped version accepted only the props common to every member of the union, so a prop belonging to just one member was rejected even though the unwrapped component accepted it.

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.