build(deps): bump @emotion/react from 11.7.1 to 11.10.6 in /website

[dependabot]

Bumps @emotion/react from 11.7.1 to 11.10.6.

Release notes

Sourced from @​emotion/react's releases.

@​emotion/react@​11.10.6

Patch Changes

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

• Updated dependencies [4e172c2a]:

  • @​emotion/babel-plugin@​11.10.6

@​emotion/react@​11.10.5

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

@​emotion/react@​11.10.4

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

@​emotion/react@​11.10.0

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

@​emotion/react@​11.9.3

Patch Changes

... (truncated)

Commits

• 0283f88 Version Packages (#2999)
• 4e172c2 Remove peer dependency on @babel/core from most packages (#2985)
• 88ce707 Add Feathery to the in the wild list (#2990)
• acb72a4 Add explicit permissions to GitHub workflows (#2899)
• 92be52d Version Packages (#2885)
• 13afe03 Upgrade Stylis to a version with container queries support (#2929)
• d8a13bc Fork Stylis prefixer (#2890)
• c1ee578 Remove unused cx import in a doc example (#2915)
• 4c0005f Do not warn about @emotion/react being loaded twice in Vitest (#2905)
• 61c6696 Do not log failed rule insertions in the speedy mode for -ms-expand and `-m...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)