Update emotion monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@emotion/react (source)	11.10.4 -> 11.14.0
@emotion/styled (source)	11.10.4 -> 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/cache@​11.13.5
  • @​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

• #​2815 65a1eea Thanks @​srmagura! - Automatic labeling at runtime is now an opt-in feature. Define globalThis.EMOTION_RUNTIME_AUTO_LABEL = true before Emotion gets initialized to enable it.

Patch Changes

• #​3206 d1994c4 Thanks @​DiegoAndai! - Improved compatibility with the upcoming @types/react for React 19 where the global JSX namespace doesn't exist anymore

• #​3208 56109e7 Thanks @​Andarist! - Only forward defined refs to improve compatibility with the upcoming React 19

• Updated dependencies [9ca22c6, b1d16b0, 16d8a8c]:

  • @​emotion/serialize@​1.2.0
  • @​emotion/weak-memoize@​0.4.0
  • @​emotion/utils@​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, 336f3d50]:

  • @​emotion/babel-plugin@​11.11.0
  • @​emotion/cache@​11.11.0
  • @​emotion/serialize@​1.1.2
  • @​emotion/use-insertion-effect-with-fallbacks@​1.0.1
  • @​emotion/utils@​1.2.1
  • @​emotion/weak-memoize@​0.3.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

---

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.

[netlify]

✅ Deploy Preview for opensesame-engineering-blog ready!

Name	Link
🔨 Latest commit	1760d63
🔍 Latest deploy log	https://app.netlify.com/projects/opensesame-engineering-blog/deploys/685d93dd9584d40007a6f348
😎 Deploy Preview	https://deploy-preview-57--opensesame-engineering-blog.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.