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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@emotion/react (source)	11.9.0 -> 11.10.4
@emotion/styled (source)	11.8.1 -> 11.10.4

---

Release Notes

emotion-js/emotion

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/is-prop-valid@​1.2.0
  • @​emotion/serialize@​1.1.0
  • @​emotion/utils@​1.2.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

---

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, click this checkbox.

---

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	Updated
website	✅ Ready (Inspect)	Visit Preview	Sep 25, 2022 at 8:29PM (UTC)