NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #2881 most downloaded on npm
Fast, expressive styling for React.
Latest stable
6.6.0
Last release 12 days ago
10 Nov 2026
Ships fairly regularly
a new release about every 2 weeks
Nearly every release is documented
notes for 59 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
10 years old
483 releases · first in 2016
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Blog post ・ Migration instructions
Blog post ・ Migration instructions
npm install --save styled-components@beta
Add warning when component is not a styled component and cannot be referred via component selector, by @egdbear (see #2070)
Fix how ampersand is handled in self-referential selector combinations, e.g. & + & (see #2071)
Add babel macro for full-featured interop with create react app v2+, by @lucleray (see #2032)
When using CRA v2, import styled components from styled-components/macro instead to gain all the benefits of our babel plugin.
Add a warning when wrapping a React component with styled() and the className isn't used (meaning styling isn't applied), by @Fer0x (see #2073)
Blog post ・ Migration instructions
Blog post ・ Migration instructions
npm install --save styled-components@beta
Add support for as to be used with attrs for better polymorphism, by @imbhargav5 (see #2055)
Fix withTheme HOC to use a theme defined in defaultProps of the wrapped component, by @theboyWhoCriedWoolf (see #2033)
Add enzymeFind test utility to easily grab instances of a styled-component from enyzme mounted testing scenarios, by @probablyup (see #2049)
import { mount } from 'enzyme';
import React from 'react';
import styled from 'styled-components';
import { enzymeFind } from 'styled-components/test-utils';
const Thing = styled.div`
color: red;
`;
const wrapper = mount(
<div>
<Thing isCool />
</div>
);
const thing = enzymeFind(wrapper, Thing);
// expect(thing.props()).toHaveProperty('isCool') etc
Blog post ・ Migration instructions
Blog post ・ Migration instructions
npm install --save styled-components@beta
keyframes with createGlobalStyle, by @probablyup (see #2029)Blog post ・ Migration instructions
Blog post ・ Migration instructions
npm install --save styled-components@beta
Blog post ・ Migration instructions
Blog post ・ Migration instructions
npm install --save styled-components@beta
Revise createGlobalStyle HMR back to the original PR code without using componentDidMount, by @probablyup (see #2017)
Some light refactoring to further reduce object allocations, by @probablyup (see #2016)
Blog post ・ Migration instructions
Blog post ・ Migration instructions
npm install --save styled-components@beta
Fix a bug introduced from some refactoring that went into beta.5 around usage of keyframes with multiple interpolations, by @probablyup (see #2013)
Tweak the styled components base component naming to look nicer in DevTools, by @probablyup (see #2012)
Beef up the error message that sometimes occurs when multiple versions of styled components are used together and the StyleSheet instance can't be found, by @probablyup (see #2012)
Blog post ・ Migration instructions
Blog post ・ Migration instructions
npm install --save styled-components@beta
Fix issue with createGlobalStyle and hot module reload, by @probablyup (see #2007)
Remove keyframes factory function, by @probablyup (see #2006)
Blog post ・ Migration instructions
Blog post ・ Migration instructions
npm install --save styled-components@beta
Note: this beta has a lot of internal changes. If you notice anything funky, please let us know. All tests are passing, etc.
Use PureComponent instead of Component for the StyledComponent base class, by @probablyup
Internal refactoring to simplify the codebase and make it more readily DCE-able, by @probablyup
Blog post ・ Migration instructions
Blog post ・ Migration instructions
npm install --save styled-components@beta
Fix an issue when streaming with very large amounts of output where sometimes styles might not make it to the client, by @probablyup (see #1996)
Fix the createGlobalStyle multiusage warning having false positives, by @probablyup (see #1993)
Blog post ・ Migration instructions
Blog post ・ Migration instructions
npm install --save styled-components@beta
Expose ThemeConsumer component, the "consumer" render prop component from the React.createContext API if people are interested in using it rather than / in addition to the withTheme HOC, @probablyup
Remove "no tags" experiment, by @probablyup (see #1987); if you are using the babel plugin, please make sure it's fully updated
Fixed an issue with createGlobalStyle when the component was composed in multiple places and render of the subsequent component instance happened before unmount of the original; previously we removed styles immediately upon unmount of any instance without checking how many copies were still alive, by @probablyup (see #1989)
Blog post ・ Migration instructions
Blog post ・ Migration instructions
npm install --save styled-components@beta
Fixed an issue where createGlobalStyle was clobbering the very next style to be applied during rehydration in production mode, by @probablyup (see #1976)
Removed some unused code, by @probablyup (see #1976)
Switched createGlobalStyle to be a PureComponent, by @probablyup (see #1976)
There's a ton of new and exciting things in v4, along with breaking changes. See the full list below:
The first beta of v4 is here! 👏🥂
Blog post ・ Migration instructions
npm install --save styled-components@beta
There's a ton of new and exciting things in v4, along with breaking changes. See the full list below:
Remove deprecated consolidateStreamedStyles API, by @probablyup (see #1906)
Remove deprecated jsnext:main entry point from package.json, by @probablyup (see #1907)
Remove deprecated .extend API, by @probablyup (see #1908)
Migrate to new context API, by @alexandernanberg (see #1894)
Remove TS typings; they are now to be found in DefinitelyTyped, by @probablyup. See https://github.com/styled-components/styled-components/issues/1778 for more information.
Add new data-styled-version attribute to generated <style> tags to allow multiple versions of styled-components to function on the page at once without clobbering each other, by @probablyup
It's still highly recommended to use aliasing via your bundler to dedupe libraries like styled-components and react.
[Breaking change] Refactor keyframes helper, by @fer0x (see #1930).
Keyframes is now implemented in a "lazy" manner: its styles will be injected with the render phase of components using them.
keyframes no longer returns an animation name, instead it returns an object which has method .getName() for the purpose of getting the animation name.
Add createGlobalStyle that returns a component which, when mounting, will apply global styles. This is a replacement for the injectGlobal API. It can be updated, replaced, removed, etc like any normal component and the global scope will update accordingly, by @JamieDixon @marionebl, @yjimk, and @imbhargav5 (see #1416)
const GlobalStyles = createGlobalStyle`
html {
color: 'red';
}
`
// then put it in your React tree somewhere:
// <GlobalStyles />
Migrate to use new React.forwardRef API, by @probablyup; note that this removes the innerRef API since it is no longer needed.
Implement styled() wrapper folding. In a nutshell, when you nest styled wrappers (e.g. styled(styled.div)) the components are now folded such that only one is mounted that contains the merged styles of its ancestors. This is conceptually equivalent to the removed "extend" functionality, but without many of the downsides -- and it's automatic, by @probablyup (see #1962)
Added a first-class API for rendering polymorphism via "as" prop. In most cases, this new prop will replace your need to use the .withComponent API. It allows you to control what underlying element or component is rendered at runtime, while not messing with the styles, by @probablyup (see #1962)
import { Link } from 'react-router'
const Component = styled.div`
color: red;
`
// Examples
<Component>Hello world!</Component>
<Component as="span">Hello world!</Component>
<Component as={Link} to="home">Hello world!</Component>
A note for preact users: if you are doing the preact-compat aliasing, it won't work with this beta because they haven't implemented React.createContext in preact-compat yet.
Nothing published for this version
Added a few iframe attributes to the valid attribute list: allow, allowUserMedia, allowPaymentRequest, by @asoltys (see #2083 and #2085)
Remove the injectGlobal warning; it's not actionable since the replacement API is in v4 only, so why say anything?
Remove the injectGlobal warning; it's not actionable since the replacement API is in v4 only, so why say anything?
Fix the injectGlobal deprecation message being improperly guarded for production
Fix the injectGlobal deprecation message being improperly guarded for production
Add warning for the upcoming removal of the injectGlobal API in v4.0, by @rainboxx (see #1867)
Add warning for the upcoming removal of the injectGlobal API in v4.0, by @rainboxx (see #1867)
Backport from v4: Beef up the error message that sometimes occurs when multiple versions of styled components are used together and the StyleSheet instance can't be found, by @probablyup (see #2012)
Fixed an issue when streaming with very large amounts of output where sometimes styles might not make it to the client, by @probablyup (see #1997)
Fixed an issue when streaming with very large amounts of output where sometimes styles might not make it to the client, by @probablyup (see #1997)
Tone down the dev warnings for deprecated APIs (they were console.error, now console.warn), by @probablyup
console.error, now console.warn), by @probablyupFix warning function not having a production fallback, by @mitoyarzun (see #1938)
Fix warning function not having a production fallback, by @mitoyarzun (see #1938)
Add warning for the upcoming removal of the extend API in v4.0, by @probablyup (see #1909)
Add warning for the upcoming removal of the extend API in v4.0, by @probablyup (see #1909)
Throw Error if a React component was mistakenly interpolated within styles, by @imbhargav5 (see #1883)
Fix the primitives build, by @probablyup (see 24f097)
Fix a regression from #1843 that breaks deferred injection and duplicates rules, by @kitten (see #1892)
Fixed a bug in typings where isStyledComponent was defined using an undefined variable, by @MayhemYDG (see #1876)
Fixed a bug in typings where isStyledComponent was defined using an undefined variable, by @MayhemYDG (see #1876)
Add error system, by @probablyup (see #1881)
Fix "stream" module not being properly eliminated by rollup, by @probablyup
Add first-class support for functions that return objects, by @acjay (see #1820)
Add first-class support for functions that return objects, by @acjay (see #1820)
const Comp = styled.div((({ color }) => ({
color,
}))
Add support for the prop variants used by Preact (autofocus, class, for), by @probablyup (see #1823)
Various performance improvements, by @probablyup (see #1843)
[TS] Revert #1798, by @Igorbek (see #1840)
[Internal] Add benchmarking suite, by @mxstbr (see #1833)
Nothing published for this version
Nothing published for this version
Fixed a regression when extending a styled(StyledComponent) introduced in 3.3.0, by @probablyup (see #1819)
Fixed a regression when extending a styled(StyledComponent) introduced in 3.3.0, by @probablyup (see #1819)
Adjust how displayName is generated when not using Babel to properly preserve a displayName passed via withConfig, by @probablyup (see #1755)
[TS] Fix props being removed when indexed types are passed to WithOptionalTheme, by @devrelm (see #1806)
[TS] Allow TypeScript 2.9.1 to accept tagged template type argument, by @Igorbek (see #1798)
Add ref documentation for React.createRef(), by @julmot (see #1792)
Nothing published for this version
Nothing published for this version
Nothing published for this version
Lots of 🔥fixes in this release! As always, thank you contributors for your hard work 🙇
Lots of 🔥fixes in this release! As always, thank you contributors for your hard work 🙇
Allow non-plain objects as ThemeProvider themes, by @phyllisstein (see #1780)
[internal] Upgrade flow-bin to latest, by @halvves (see #1748)
[internal] Update various CI bits, by @probablyup (see #1769)
Reimplement SSR stream handling as a transform stream rather than a second-order readable stream, by @probablyup (see #1768)
Allow React Component as attr, by @valerybugakov (see #1751)
Added pointer events to valid attributes check, by @plankguy (see #1790)
Note: v3.3.1 was skipped due to a bad deploy.
Nothing published for this version
Nothing published for this version
The team is very excited to release v3.3.0, containing a number of important bugfixes and quality of life improvements to the library! This will proba
The team is very excited to release v3.3.0, containing a number of important bugfixes and quality of life improvements to the library! This will probably be the last feature release before v4.0 (roadmap) this summer.
Thank you so much to all the people who contributed. styled-components is nothing without its community ❤️
Fix off-by-one error in insertRuleHelpers.js, by @migueloller (see #1749)
Add first-class support for objects, by @mxstbr (see #1732)
const Component = styled.div({
color: 'blue'
})
Fix typo in console warning about multiple instances, by @lucianbuzzo (see #1730)
Make the multiple instance warning criteria a little more strict to avoid badgering people running unit tests, by @probablyup (see #1693)
Fix React.createRef() values for innerRef being ignored in React Native, by @simonbuchan (see #1718)
Hoist non-react static properties on wrapped classes, by @probablyup (see #1750)
Support attributes prefixed by x-, by @mlecoq (see #1753)
The primary fix in this patch release was related to a misconfiguration in the stylis rule splitter which could cause some rules to be discarded when
The primary fix in this patch release was related to a misconfiguration in the stylis rule splitter which could cause some rules to be discarded when there was no whitespace around selector operands.
Nothing published for this version
Make sure that you're installing v3.2.5 as v3.2.4 was missing some postinstall scripts for our OpenCollective message 😅
Make sure that you're installing v3.2.5 as v3.2.4 was missing some postinstall scripts for our OpenCollective message 😅
The preprocess option was never here to stay and its experiment has essentially proven to be insufficient for our future goals. Check out Sweetsour/ISTF for our current effort of making styled-components more performant and adding a CSS pipeline to it: https://github.com/kitten/sweetsour
Thanks to @Samatar26 for his PR!
process.env.SC_ATTR to override our style tag's marker attributeWhile we're figuring out how to improve our context-drive StyleSheetManager in a stable way that works with SSR and sharded stylesheets, we would still like to provide a way for you to use styled-components that enables widgets and other use-cases where it might be necessary to prevent us from destroying your stylesheet on pages.
Specifically this affects people who are building non-SSR code that runs on pages where styled-components is already in place. In these cases our SSR rehydration would go along and happily remove another module's style tags. We haven't considered this closely as it is not a good practice in our eyes to run duplicated styled-components modules in a single app. But when you're not dealing with a single app only it might make sense.
You can now change the the style tag's styled-components attribute by bundling with the SC_ATTR environment variable. Given a setup where you can set this variable, we will now inject style tags with a different attribute, so that they're not affected by the standard SSR rehydration.
Documentation will follow soon; Thanks to @Fer0x for this change!
This release simply frees up some memory by removing cloned StyleSheets when they're not needed anymore.
This release simply frees up some memory by removing cloned StyleSheets when they're not needed anymore.
Nothing published for this version
If you've noticed that v3.2 would cause your server-side rendered app to output all styles it knows of, you weren't alone!
If you've noticed that v3.2 would cause your server-side rendered app to output all styles it knows of, you weren't alone!
The ServerTag was accidentally cloning itself incorrectly. This meant that the ServerStyleSheet would inherit the same server styles from the “master” StyleSheet.
We now clone the tag correctly and a test is in place to ensure this doesn't happen again, since this bug came up a couple of times in past v2 releases. Thanks to @DeividasK for reporting this bug!
Have some styles gone missing? In the newer >=3.1 versions that introduced speedy mode (i.e. insertRule support) some rules might not have been injected properly. This came down to insertRule being more strict with what we add. In development an incorrectly formatted CSS rule might not cause much trouble, but in production insertRule complains about it.
Stylis, more specifically stylis-rule-sheet, was generating invalid CSS when at-rules were nested inside style rules. For instance the following CSS would cause trouble:
/* input */
&:hover {
@media (min-width: 768px) { color: papayahwip; }
}
/* incorrect output */
@media (min-width: 768px) {
&:hover { color: papayahwip; }
}}
/* ^ note the extra closing curly brace */
/* v3.2.2 fixed output */
@media (min-width: 768px) {
&:hover { color: papayahwip; }
}
IS_BROWSER detectionBefore v3.2.2 we would check whether styled-components is running inside the browser using: typeof window !== 'undefined'. This proofed insufficient in a couple of special cases for some people, so we have now added 'HTMLElement' in window to this check.
Thanks to @danieldunderfelt for contributing this fix!
Nothing published for this version
Nothing published for this version
We accidentally removed dangerouslySetInnerHtml in our SSR output with just some children string. This would cause some characters to be encoded.
We accidentally removed dangerouslySetInnerHtml in our SSR output with just some children string. This would cause some characters to be encoded.
We have corrected this mistake and more unit tests are now in place to prevent this from happening again. Thanks to @misund for reporting this mistake!
@import at-rules@import rules must appear at the top of style sheets (i.e tags).
In older versions we used to shard our style tags into local and global ones. Because any CSS that is being passed to us is also reordered, so that @import rules appear at the top, often this would mean that a lone injectGlobal would get away with @import rules.
This wasn't sufficient as using @import in a component (obviously unsupported and not recommended) or in another consecutive injectGlobal would cause this logic to break, since @import wouldn't appear at the top of the stylesheet anymore.
This oversight was made worse by the fact that we stopped sharding local and global style tags. This would mean that @import could now show up fairly late in a stylesheet, instead of at its top.
In this version we introduce a patch that creates an additional style tag at the top of all other ones that we create, when necessary, which is going to accept all @import rules separately. So when you use injectGlobal and pass it an @import rule, it will now be stripped out of the rest of your CSS, and put into a completely isolated style tag.
Nothing published for this version
Nothing published for this version
Nothing published for this version
…injecting global styles as well. This is not a breaking change, but produces the same behaviour and specificity as it did before. (Change)
This is a small minor release that introduces a couple of minor changes, but also a complete rewrite of our StyleSheet implementation. Not only is it smaller, but it also lowers the barrier to entry for new contributors (like yourself, dear reader, hopefully!) to read and understand it, and eventually contribute great new features!
consolidateStreamedStylesIf you’ve recently migrated to streamed server-side-rendered styles, then you will be familiar with our consolidateStreamedStyles function, which was an “extended rehydration” that moved all streamed styled-components style tags when called.
Due to our refactor of our StyleSheet behaviour (see below), our new rehydration implementation now takes care of this for you automatically.
This function will now output a deprecation warning when it’s being used and effectively does nothing at all. (Take a look at its source for more information)
StyleSheet and ServerStyleSheetWe now handle the style rules around a “style tag” based approach, which also means that our BrowserStyleSheet is a thing of the past. Depending on the environment, we will now switch between server, browser, and insertRule style tags, which all abstract their internal behaviour.
The concept of “local” vs “global” styles has been removed, in anticipation of some upcoming, future APIs, and our rehydration has been rewritten as well. You will see only a single style tag after rehydration, and now splits between style tags when injecting global styles as well. This is not a breaking change, but produces the same behaviour and specificity as it did before. (Change)
You will also notice a couple of improved and more detailed error messages—if you ever run into them that is—which will help you to understand some things that might go wrong more easily. (Change)
Style tags will now also be injected consecutively in the DOM. This means that styled-components won’t append them to the target, but will append them to its last style tag, if a first one was already injected. This should help you to predict the order of injection, when dealing with external CSS. (Change)
You can now pass an element to a StyleSheetManager and all the components in its context below in the tree will add their styles to new tags in the specified target.
While this is not guaranteed to work with SSR yet, it can help you to easily add runtime-styles to a different part of the DOM. For example the shadow DOM.
Starting from this version, style-components will log a warning when multiple instances of it are being bundled and run on the same page. Due to our rehydration this can lead to errors, where one instance of styled-components will interfere with the other. This is why we have decided to add a small warning notifying you of this, since we don’t see the practice of adding multiple styled-components instances to a single page as a best practice.
Please note that this warning won’t show up, when older version of styled-components are present, as they don’t contain the code necessary to be detected.
StyleSheet.remove API (Internal)This is an internal API that allows us to remove rules and components from our StyleSheets, which will come in handy for some new APIs for global styles quite soon.
We accidentally disabled semicolon autocompletion in stylis, which accidentally introduced an unnoticed breaking change in a past version a while back.
Semicolon autocompletion is now enabled and back again. Thanks to @Blasz for reporting this mistake!
insertRule aka production modeOur version of stylis-rule-sheet was updated which fixes nested media queries which can now be used as is expected in production. (see #1529 and #1528)
type="text/css"-attribute from style tag to remove warnings from w3c validator (see #1551)Thanks to the numerous contributors and maintainers who have worked towards this release. We're sorry if some names are missing, so thanks additionally goes out to everyone who’s worked hard to get v3 out!
(In no particular order)
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Bugfix for the last style tag sometimes being emitted multiple times during streaming (see #1479)
Bugfix for the last style tag sometimes being emitted multiple times during streaming (see #1479)
Bugfix for speedy mode rehydration and added handling for out-of-order style injection (see #1482)
NOTE: When calling consolidateStreamedStyles() after streaming, make sure it is called as early in the bundle as possible.
styled-components injects new CSS upon construction of new components not prerender, so consolidation must happen before any new CSS is injected on the page.
One column per quarter.