fix(deps): update emotion monorepo to v11.10.6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@emotion/react (source)	11.10.0 -> 11.10.6
@emotion/styled (source)	11.10.0 -> 11.10.6

---

Release Notes

emotion-js/emotion

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

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

• Updated dependencies [13afe030, c02b1214]:

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

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

---

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.

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

---

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

---

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
nextjs-typescript-chakra	❌ Failed (Inspect)			Mar 12, 2023 at 7:44PM (UTC)

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

installing v2 tool node v18.15.0
linking tool node v18.15.0
node: v18.15.0 /usr/local/bin/node
npm: 9.5.0  /usr/local/bin/npm
Installed v2 /usr/local/buildpack/tools/v2/node.sh in 4 seconds
skip cleanup, not a docker build: 154b1867a1c5
installing v2 tool pnpm v7.29.1