npm / @emotion/jest

@emotion/jest

What changed in @emotion/jest 10 to 11, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-25.

6 breaking2 new APIs and options3 tooling

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@emotion/jest 111 changes

@types/jest@30.x is now allowed as an optional peer dependency.
11.14.2release notes

Emotion 10 makes underlying class names harder to access; using class names directly does not provide features like zero-config server rendering.
10.0.0upgrade guide
Emotion 10 shifts style composition from combining generated class names with cx to composing styles in the css prop.
10.0.0upgrade guide
Migrate styled imports from react-emotion to @emotion/styled, with Emotion exports in a separate import.
10.0.0upgrade guide
Replace injectGlobal usage with Global styles.
10.0.0upgrade guide
Using the css prop requires importing jsx and setting the JSX pragma at the top of the source file.
10.0.0upgrade guide
Emotion 10 requires React 16.3 or greater.
10.0.0upgrade guide

Add a compat cache provider while the app still uses css, keyframes or injectGlobal from emotion; remove it after those usages are gone.
10.0.0upgrade guide
Use ClassNames to generate styles for components that accept props such as wrapperClassName.
10.0.0upgrade guide

Migrate css usage that generates a class name to the css prop.
10.0.0upgrade guide
The plugin can automate the first part of the incremental migration to Emotion 10.
10.0.0upgrade guide