NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #1717 most downloaded on npm
serialization utils for emotion
Latest stable
1.3.3
Last release 2 years ago
no release in 18 months
Release timing varies
gaps range from 4 weeks to 12 months
Some releases are documented
notes for 32 of 56 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
68 releases · first in 2018
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
Updated dependencies \[`77d930d`]:
#3270 77d930d Thanks @emmatown! - Fix inconsistent hashes using development vs production bundles/exports conditions when using @emotion/babel-plugin with sourceMap: true (the default). This is particularly visible when using Emotion with the Next.js Pages router where the development condition is used when bundling code but not when importing external code with Node.js.
Updated dependencies [77d930d]:
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Updated dependencies \[`ad630e3`]:
### Patch Changes - #3093 `532ff57` Thanks @codejet, @DustinBrett! - Adds fetchpriority and fetchPriority to the list of allowed props.
532ff57 Thanks @codejet, @DustinBrett! - Adds fetchpriority and fetchPriority to the list of allowed props.153cf88]:
Development builds (and other environment-specific builds) can be used by using proper conditions (see here). Most modern bundlers/frameworks already
#3198 d8ff8a5 Thanks @Andarist! - Migrated away from relying on process.env.NODE_ENV checks to differentiate between production and development builds.
Development builds (and other environment-specific builds) can be used by using proper conditions (see here). Most modern bundlers/frameworks already preconfigure those for the user so no action has to be taken.
Default files should continue to work in all environments.
16d8a8c Thanks @rjdestigter! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.52aadc6 Thanks @sarayourfriend! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.52aadc6 Thanks @sarayourfriend! - Type declaration for StyleSheet's constructor has been fixed. It incorrectly was specifying that options were optional when in reality they weren't.a1e881b Thanks @sarayourfriend! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.7f8db2d]:
### Minor Changes - #2819 `bbad8c79` Thanks @nicksrandall! - exports field has been added to the package.json manifest. It limits what files can be im
#2819 bbad8c79 Thanks @nicksrandall! - exports field has been added to the package.json manifest. It limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.
#2819 bbad8c79 Thanks @nicksrandall! - Thanks to the added exports field, the package now includes a worker condition that can be utilized by properly configured bundlers when targeting worker-like environments. It fixes the issue with browser-specific files being prioritized by some bundlers when targeting workers.
bbad8c79 Thanks @nicksrandall! - exports field has been added to the package.json manifest. It limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.bbad8c79]:
9ca22c6 Thanks @danilofuchs! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.Updated dependencies \[`7f8db2d`]:
7f8db2d]:
c9b84dbe Thanks @Cerber-Ursi! - Make ArrayInterpolation to extend ReadonlyArray to match a similar recent change to ArrayCSSInterpolation. It fixes some compatibility issues when those 2 get mixed together.### Patch Changes - #2759 Thanks @srmagura! - Change the type of the argument to isPropValid from PropertyKey to string in the TypeScript definitions.
45c440fb Thanks @Cerber-Ursi! - Replace arrays with readonly arrays in CSS type definitions, following changes in csstype### Patch Changes - #2621 `d2531639` Thanks @andreasmcdermott! - Added `abbr` prop to the allowlist of forwardable props.
d2531639 Thanks @andreasmcdermott! - Added abbr prop to the allowlist of forwardable props.### Patch Changes - #2728 `6c2d7a60` Thanks @Peeja! - TypeScript type for the container option has been adjusted. It will now accept a ShadowRoot, or
Updated dependencies \[`bbad8c79`, `bbad8c79`]:
bbad8c79 Thanks @nicksrandall! - exports field has been added to the package.json manifest. It limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.#3198 d8ff8a5 Thanks @Andarist! - Migrated away from relying on process.env.NODE_ENV checks to differentiate between production and development builds.
Development builds (and other environment-specific builds) can be used by using proper conditions (see here). Most modern bundlers/frameworks already preconfigure those for the user so no action has to be taken.
Default files should continue to work in all environments.
#3215 a9f6912 Thanks @Andarist! - Added edge-light and workerd conditions to package.json manifest to better serve users using Vercel Edge and Cloudflare Workers.
### Patch Changes - #2727 `26e4e3e8` Thanks @srmagura! - Changed the error message "Component selectors can only be used in conjunction with @emotion/
#2727 26e4e3e8 Thanks @srmagura! - Changed the error message "Component selectors can only be used in conjunction with @emotion/babel-plugin" to reference the new SWC Emotion plugin which will support component selectors soon.
#2572 5e81f213 Thanks @otakustay! - Changed the registered parameter to be declared as optional in the TypeScript definition to match the runtime requirement.
### Patch Changes - #2700 `d9357621` Thanks @arturmuller! - Fixed a false positive warning for content properties that included var().
d9357621 Thanks @arturmuller! - Fixed a false positive warning for content properties that included var().f2eda829 Thanks @mdesantis! - Fixed an issue with sheet.flush() crashing if its style elements were already detached by something else.`662f0e0f` #2335 Thanks @iChenLei! - Fixed appending manual labels to Babel-optimized style objects.
405af5ca Thanks @layershifter! - Do not log failed rule insertions in the speedy mode for even more vendor-prefixed pseudo-elements/classes like :-moz-focus-inner, :-moz-focusring, and :-ms-clear.### Patch Changes - #2590 `1554a7e2` Thanks @Andarist! - Upgraded and pinned the version of Stylis - the CSS parser that Emotion uses under the hood.
418daad9 #2264 Thanks @lucasweng! - Fix incorrectly throwing error on the gradient content values`9e998e37` #1817 Thanks @Andarist! - insertStyles no longer calls cache.insert with a scoped class name as a selector when inserting keyframes. The ch
9e998e37 #1817 Thanks @Andarist! - @import rules are no longer special-cased - they no longer are always inserted at the beginning of the stylesheet. The responsibility to put them first has been moved to a consumer of this package.4a891bf6 #1473 Thanks @jcharry! - The new prepend option can make Emotion add style tags at the beginning of the specified DOM container instead of the end.
dfe79aca #1696 Thanks @Andarist! - Added hydrate method which can be used for SSRed styles. They become a part of a sheet and can be flushed.
42df3f3b #2028 Thanks @Andarist! - Generated style elements got data-s="1" attribute so @emotion/cache can recognize them as being already owned by another Emotion copy to avoid messing up existing style elements when initializing a new copy.
1e4a741d #1697 Thanks @Andarist! - Removed mentions of maxLength option in types & docs as it has been removed some time ago.
c6431074 #1609 Thanks @tomsseisums! - Reworked Interpolation-related types. Correct types should now be provided to all flavours of Emotion.5d692a6a #1956 Thanks @eps1lon! - Upgraded csstype dependency to its v3. This is what we use to provide TypeScript typings for object styles. The upgrade should not affect any consuming code but it's worth mentioning if any edge case scenarios arise.e3d7db87 #1732 Thanks @Andarist! - An additional semicolon is now inserted after interpolated arrays to cover cases when it doesn't have a trailing semi itself and thus breaking composition with styles coming after it.
8a896a31 #1611 Thanks @Andarist! - Throw error about invalid content property values instead of just logging error to the console.
5c55fd17 #1653 Thanks @Andarist! - Fix to what location generated source maps are pointing in case of composed styles.
a085003d #1613 Thanks @Andarist! - Add missing #__PURE__ annotations
Updated dependencies [debaad9a, 9e998e37]:
923ded01 #1643 Thanks @JakeGinnivan! - Allow isPropValid to take any PropertyKey as an argument (instead of just string).69446cb5 #1971 Thanks @mjcampagna! - translate got added to the list of the valid props.`9c4ebc16` #2030 Thanks @Andarist! - Release candidate version.
`42df3f3b` #2028 Thanks @Andarist! - Generated style elements got data-s="1" attribute so @emotion/cache can recognize them as being already owned by
76e3dc4d #2009 Thanks @Andarist! - Re-release latest prerelease version of this package as it has incorrectly been "downgraded" to 0.x version due to a bug in Changesets. This has caused problems because Emotion 10 had a newer 0.x release and thus version targeting Emotion 10 has been fetched on installs as it has been satisfying the specified dependency range.`5d692a6a` #1956 Thanks @eps1lon! - Upgraded `csstype` dependency to its v3. This is what we use to provide TypeScript typings for object styles. The
`debaad9a` #1999 Thanks @RoystonS! - Fixed TypeScript definition of the EmotionCache by replacing the non-existent stylis method with insert that is a
…and let them be inferred. Otherwise refer to the breaking changes list below.
a72e6dc0 #1501 Thanks @JakeGinnivan! - TypeScript types have been restructured. These changes:
If you encounter build issues after upgrade, try removing any manually specified generic types and let them be inferred. Otherwise refer to the breaking changes list below.
withTheme can now have the Theme type specified when calling it. For example withTheme<MyTheme>(MyComponent)
Breaking change: Generic argument changed, if you were specifying the ComponentType you will need to remove the generic parameter. Recommend following example setup in the TypeScript docs under theming section
css function has been restricted to prevent passing of invalid types
CreateStyled functions no longer take a second ExtraProps argument. Instead move it to after the create styled call. For example
styled<typeof MyComponent, ExtraProps>(MyComponent)({})
to
styled(MyComponent)<ExtraProps>({})
StyledComponent type no longer supports the third generic Theme parameter. Instead add the theme prop to the first Props argument. For example:
StyledComponent<Props, {}, MyTheme>
to
StyledComponent<Props & { theme?: MyTheme }>
`c643107` #1609 Thanks @joltmode! - Reworked Interpolation-related types. Correct types should now be provided to all flavours of emotion.
Updated dependencies [`446e756`]:
446e756]:
`4c62ae9` #1698 Thanks @Andarist! - Add LICENSE file
Updated dependencies [`debaad9a`]:
debaad9a]:
Updated dependencies [`9e998e37`]:
9e998e37]:
`8a896a31` #1611 Thanks @Andarist! - Throw error about invalid content property values instead of just logging error to the console.
`a55f3d49` #1581 Thanks @Andarist! - Don't cause invalid rule to be serialized when using object style with falsy value
`3b7e2f2e` Thanks @emmatown! - Fix flow errors
`4fc5657a` #1219 Thanks @Andarist! - Add dev hint about css object being stringified by accident
Updated dependencies [c81c0033]:
66cda641 #1478 Thanks @Andarist! - Add warnings about using illegal escape sequences
c257d2a3 #1420 Thanks @Andarist! - Fix for opaque keyframes object being used as value for animation & animationName in object styles
c0eb604d #1419 Thanks @emmatown! - Update build tool
757bd86d #1378 Thanks @Andarist! - Fixed issue with camelCased custom properties not being handled correctly in object styles
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
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
Nothing published for this version
Nothing published for this version
Nothing published for this version
### Minor Changes - #3240 `153cf88` Thanks @justinfernald! - Add scale property as unitless
153cf88 Thanks @justinfernald! - Add scale property as unitless### Patch Changes - #3029 `eed5e6cf` Thanks @Andarist! - Fixed importing in Node ESM
### Minor Changes - #2819 `bbad8c79` Thanks @nicksrandall! - exports field has been added to the package.json manifest. It limits what files can be im
bbad8c79 Thanks @nicksrandall! - exports field has been added to the package.json manifest. It limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.fc4d27c Thanks @sarayourfriend! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.7f8db2d Thanks @sarayourfriend! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.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
### Patch Changes - #3029 `eed5e6cf` Thanks @Andarist! - Fixed importing in Node ESM - #3012 `e6e5b3d7` Thanks @sgrishchenko! - Add aspectRatio as a u
### Minor Changes - #2819 `bbad8c79` Thanks @nicksrandall! - exports field has been added to the package.json manifest. It limits what files can be im
bbad8c79 Thanks @nicksrandall! - exports field has been added to the package.json manifest. It limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.One column per quarter.