Update emotion monorepo

[renovate]

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package	Change	Age	Confidence
@emotion/react (source)	11.4.1 -> 11.14.0
@emotion/styled (source)	11.3.0 -> 11.14.1

---

Release Notes

emotion-js/emotion (@​emotion/react)

v11.14.0

Compare Source

Minor Changes

• #​3281 fc4d7bd Thanks @​Andarist! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.

Patch Changes

• Updated dependencies [8dc1a6d, e1bf17e]:
  • @​emotion/cache@​11.14.0
  • @​emotion/use-insertion-effect-with-fallbacks@​1.2.0

v11.13.5

Compare Source

Patch Changes

• #​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]:

  • @​emotion/serialize@​1.3.3
  • @​emotion/utils@​1.4.2
  • @​emotion/babel-plugin@​11.13.5

v11.13.3

Compare Source

Patch Changes

• #​3232 0ce3ed0 Thanks @​ENvironmentSet! - Distribute css prop attachment over props that are union types

• Updated dependencies []:

  • @​emotion/serialize@​1.3.1

v11.13.0

Compare Source

Minor Changes

• #​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

• Updated dependencies [d8ff8a5, a9f6912]:
  • @​emotion/cache@​11.13.0
  • @​emotion/serialize@​1.3.0
  • @​emotion/use-insertion-effect-with-fallbacks@​1.1.0
  • @​emotion/utils@​1.4.0

v11.12.0

Compare Source

Minor Changes

• #​2558 85772c3 Thanks @​emmatown! - Source code has been migrated to TypeScript. From now on type declarations will be emitted based on that, instead of being hand-written.

Patch Changes

• #​2558 85772c3 Thanks @​emmatown! - Fixed options parameter to createEmotion from @emotion/css/create-instance incorrectly being marked as optional when it's required.

• Updated dependencies [9ca22c6, 16d8a8c, 52aadc6, 52aadc6]:

  • @​emotion/serialize@​1.2.0
  • @​emotion/utils@​1.3.0
  • @​emotion/sheet@​1.3.0
  • @​emotion/babel-plugin@​11.12.0
  • @​emotion/cache@​11.12.0

v11.11.4

Compare Source

Patch Changes

• #​3159 5b82631d Thanks @​iegik! - Renamed an internal hasOwnProperty to hasOwn. This avoids problems in CommonJS environments when the consumer tries to prevent prototype pollution with Object.freeze(Object.prototype).

v11.11.3

Compare Source

Patch Changes

• #​3101 49c20b4f Thanks @​kyvong! - Fix Theme import for newer Typescript module resolution modes

• Updated dependencies [45c440fb]:

  • @​emotion/serialize@​1.1.3

v11.11.1

Compare Source

Patch Changes

• #​3048 9357f337 Thanks @​naari3! - Added ElementType to the Emotion's JSX namespace. It's defined in the same way as the one in @types/react and should make it possible to use components that return strings, Promises and other types that are valid in React.

v11.11.0

Compare Source

Minor Changes

• #​3031 336f3d50 Thanks @​Andarist! - Added support for cascade @layers by updating the underlying parser (stylis).

Patch Changes

• #​3029 eed5e6cf Thanks @​Andarist! - Fixed importing in Node ESM

• Updated dependencies [336f3d50, eed5e6cf]:

  • @​emotion/babel-plugin@​11.11.0
  • @​emotion/is-prop-valid@​1.2.1
  • @​emotion/serialize@​1.1.2
  • @​emotion/use-insertion-effect-with-fallbacks@​1.0.1
  • @​emotion/utils@​1.2.1

v11.10.8

Compare Source

Patch Changes

• #​3025 6bd13425 Thanks @​Andarist! - Fixed a parsing issue with & within nested functions in declaration values by updating the underlying parser (stylis).

• Updated dependencies [6bd13425, 6bd13425]:

  • @​emotion/babel-plugin@​11.10.8
  • @​emotion/cache@​11.10.8

v11.10.6

Compare Source

Patch Changes

• #​2985 4e172c2a Thanks @​emmatown! - Remove peer dependency on @babel/core

• Updated dependencies [4e172c2a]:

  • @​emotion/babel-plugin@​11.10.6

v11.10.5

Compare Source

Patch Changes

• #​2905 4c0005f6 Thanks @​p-m-p! - Do not warn about @emotion/react being loaded twice in Vitest as that might easily happen with mocked modules.

• #​2929 13afe030 Thanks @​Andarist! - The support for @container queries has been added by updating the underlying parser (stylis) .

• Updated dependencies [13afe030, c02b1214, d8a13bca]:

  • @​emotion/babel-plugin@​11.10.5
  • @​emotion/serialize@​1.1.1
  • @​emotion/cache@​11.10.5

v11.10.4

Compare Source

Patch Changes

• #​2867 89b6dbb3 Thanks @​Andarist! - Externalized code referencing React.useInsertionEffect to a separate @emotion/use-insertion-effect-with-fallbacks package. This package should be used in your defined externals if you bundle Emotion for whatever reason. It references useInsertionEffect in a very specific way that allows us to use it conditionally. However, if the code consuming Emotion is bundled as a library with Emotion in it then some bundlers might change the way in which we reference useInsertionEffect and that might create problems for bundlers used to consume the said library code. By externalizing this new package you can still bundle Emotion if you want to without running into this problem as you won't "destroy" the carefully crafted reference to useInsertionEffect in the process.

  Note that we don't recommend bundling Emotion. You should have very specific reasons to do so.

• Updated dependencies [89b6dbb3]:

  • @​emotion/use-insertion-effect-with-fallbacks@​1.0.0

v11.10.0

Compare Source

Minor Changes

• #​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.

Patch Changes

• Updated dependencies [bbad8c79, bbad8c79]:
  • @​emotion/babel-plugin@​11.10.0
  • @​emotion/cache@​11.10.0
  • @​emotion/serialize@​1.1.0
  • @​emotion/utils@​1.2.0
  • @​emotion/weak-memoize@​0.3.0

v11.9.3

Compare Source

Patch Changes

• #​2759 Thanks @​srmagura, @​Andarist! - Change the argument of the shouldForwardProp option of styled from PropertyKey to string in the TypeScript definitions.

• #​2333 3055efdd Thanks @​Andarist! - shouldForwardProp has been changed from being a bivariant method to a contravariant function - it improves the type-safety for those that type this option.

• #​2333 3055efdd Thanks @​antongolub! - FilteringStyledOptions and StyledOptions types no longer require a type argument for the Props generic.

• Updated dependencies [26e4e3e8, 5e81f213, 3055efdd]:

  • @​emotion/serialize@​1.0.4
  • @​emotion/is-prop-valid@​1.1.3

v11.9.0

Compare Source

Patch Changes

• #​2700 d9357621 Thanks @​arturmuller! - Fixed a false positive warning for content properties that included var().

• Updated dependencies [d9357621]:

  • @​emotion/serialize@​1.0.3

v11.8.2

Compare Source

Patch Changes

• #​2677 ff3cb164 Thanks @​Jack-Works! - Change Global component to use the StyleSheet constructor of the current cache.sheet. This is useful when cache.sheet is not the default implementation. Thanks to that the inner sheet constructed by Global can share the behavior with its "main" sheet that is hold by the cache.

v11.8.1

Compare Source

Patch Changes

• #​2651 39ac5b99 Thanks @​Andarist! - Fixed a transpilation issue that caused useInsertionEffect to be referenced directly in the specifiers list of the import statement. This has caused build errors in the consuming tools since the import statement can only reference known exports of a module.

v11.8.0

Compare Source

Minor Changes

• #​2600 2f27156a Thanks @​Andarist! - Refactored code to use the upcoming React.useInsertionEffect when it's available (this is a new hook that is going to be introduced in React 18). This shouldn't have any effect on existing codebases and the change should be transparent.

Patch Changes

• Updated dependencies [d2531639, 2f27156a]:
  • @​emotion/is-prop-valid@​1.1.2
  • @​emotion/utils@​1.1.0

v11.7.1

Compare Source

Patch Changes

• #​2590 1554a7e2 Thanks @​Andarist! - Upgraded and pinned the version of Stylis - the CSS parser that Emotion uses under the hood.

• Updated dependencies [1554a7e2]:

  • @​emotion/babel-plugin@​11.7.1
  • @​emotion/cache@​11.7.1

v11.7.0

Compare Source

Patch Changes

• #​2534 57be9e8c Thanks @​srmagura! - Changed the implementation of the runtime label extraction in elements using the css prop (that only happens in development) to one that should yield more consistent results across browsers. This fixes some minor issues with React reporting hydration mismatches that wouldn't happen in production.

v11.6.0

Compare Source

Minor Changes

• #​2542 eb013d25 Thanks @​eps1lon! - Fixed hydration mismatches if React.useId (an upcoming API in React 18) is used within a tree below our components.

Patch Changes

• Updated dependencies [9861a18b]:
  • @​emotion/is-prop-valid@​1.1.1

v11.5.0

Compare Source

Patch Changes

• #​2498 e5beae8e Thanks @​Andarist! - Fixed an edge case issue with incorrect rules being generated. When a context selector (&) was used not at the beginning of a selector (which is not valid SCSS but is allowed by the Stylis parser that we are using) within a group of selectors containing a pseudoclass then it was not replaced correctly with the current context selector.

• Updated dependencies [e5beae8e, 9ae4a91a, f2eda829]:

  • @​emotion/cache@​11.5.0
  • @​emotion/sheet@​1.0.3

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nszknao/generative-art/G5MAQ1m44iknrWYmRNAypg8dfKYh
✅ Preview: https://generative-art-git-renovate-emotion-monorepo-nszknao.vercel.app

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
generative-art	Error			Aug 19, 2025 6:54pm