Update dependency @emotion/core to v11

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@emotion/core	^10.0.15 -> ^11.0.0

---

Release Notes

emotion-js/emotion

v11.0.0

Compare Source

Major Changes

• b8476e08 #​1675 Thanks @​mitchellhamilton! - Rename @emotion/core to @emotion/react. Please change any imports of @emotion/core to import @emotion/react or use the @emotion/pkg-renaming ESLint rule from @emotion/eslint-plugin.

v10.3.1

Compare Source

Patch Changes

• #​2576 33c01578 Thanks @​Methuselah96! - Export Keyframes type to avoid TypeScript inserting import("@​emotion/serialize").Keyframes references into declaration files emitted based on a source files exporting keyframes result. This avoids issues with strict package managers that don't allow accessing undeclared dependencies.

v10.3.0

Compare Source

Minor Changes

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

• #​2560 b5a26619 Thanks @​eps1lon! - Dropped usage of a deprecated SFC React type in favor of FC. The FC type has been introduced in @types/[email protected] so this version of this package is now a minimum requirement for TypeScript users.

v10.1.1

Compare Source

Patch Changes

• fe30cbd6 #​2066 Thanks @​Andarist! - Fixed an issue with React giving warning about static children not having unique keys when using the classic jsx factory. This example illustrates the situation in which this has been incorrectly happening:

  <div css={{ color: 'hotpink' }}>
    <div />
    <div />
  </div>

v10.1.0

Compare Source

Minor Changes

• 71514b06 #​1970 Thanks @​FLGMwt! - Support for the new JSX runtimes has been added. They require compatible React versions and shouldn't be manually used.

  To use them you can use the new @jsxImportSource @​emotion/core pragma instead of the old @jsx jsx or you can use @emotion/babel-preset-css-prop with { runtime: 'automatic' } option to have it handled automatically for you for the whole project.

v10.0.35

Compare Source

Patch Changes

• 2cf3b16b #​1973 Thanks @​santialbo! - Fixed label extraction from the stack traces in node for components wrapped in React.forwardRef. This has affected only development builds.

v10.0.34

Compare Source

Patch Changes

• 4979ebb2 #​1966 Thanks @​chnakamura! - Fixed label extraction from the stack traces in Chrome in certain scenarios. This has affected only development builds.

v10.0.28

Compare Source

Patch Changes

• d0b2a94 #​1714 Thanks @​Andarist! - Fixed label extraction from the stack traces in FireFox and Safari. We have failed to match a label in Emotion wrappers like Theme UI which caused SSR mismatches in mentioned browsers. This has affected only development builds.

v10.0.27

Compare Source

Patch Changes

• 4c62ae9 #​1698 Thanks @​Andarist! - Add LICENSE file
• Updated dependencies [4c62ae9]:
  • @​emotion/cache@​10.0.27
  • @​emotion/css@​10.0.27
  • [email protected]
  • [email protected]
  • [email protected]
  • @​emotion/serialize@​0.11.15
  • @​emotion/sheet@​0.9.4
  • @​emotion/styled@​10.0.27
  • @​emotion/utils@​0.11.3

v10.0.22

Compare Source

Patch Changes

• 4fc5657a #​1219 Thanks @​Andarist! - Add dev hint about css object being stringified by accident

• 2fc75f26 #​1548 Thanks @​Andarist! - Accept objects as className in jsx-created components (they are stringified) to match React behavior

• 10211951 #​1553 Thanks @​Andarist! - Add dev warning about keyframes being interpolated into plain strings.

• 57a767ea #​1560 Thanks @​Andarist! - Fix composition of styles without a final semicolon in a declaration block

• Updated dependencies [4fc5657a, 10211951, 57a767ea, c3f0bc10, 11bea3a8]:

  • @​emotion/serialize@​0.11.12
  • @​emotion/styled@​10.0.22
  • @​emotion/css@​10.0.22

v10.0.21

Compare Source

Patch Changes

• 7855db4a #​1537 Thanks @​Andarist! - Add missing /* #__PURE__ */ annotation to creation of EmotionCssPropInternal

v10.0.20

Compare Source

Patch Changes

• 38bb2b19 #​1530 Thanks @​Andarist! - Fix class not being applied when putting nil as css prop value on wrapper component

v10.0.17

Compare Source

---

Configuration

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

🚦 Automerge: Enabled.

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Mend Renovate. View repository job log here.