Skip to content
This repository was archived by the owner on Nov 10, 2023. It is now read-only.

fix(deps): update dependency @emotion/react to v11.11.1 - #16

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/emotion-monorepo
Open

fix(deps): update dependency @emotion/react to v11.11.1#16
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/emotion-monorepo

Conversation

@renovate

@renovate renovate Bot commented Mar 13, 2022

Copy link
Copy Markdown

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@emotion/react (source) 11.8.1 -> 11.11.1 age adoption passing confidence

Release Notes

emotion-js/emotion (@​emotion/react)

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

Patch Changes

v11.10.8

Compare Source

Patch Changes

v11.10.6

Compare Source

Patch Changes

v11.10.5

Compare Source

Patch Changes

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]:

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.
Patch Changes

v11.9.3

Compare Source

Patch Changes

v11.9.0

Compare Source

Patch Changes

v11.8.2

Compare Source

Patch Changes
  • #​2677 ff3cb164 Thanks @​Jack-Works! - Change Global component to use the StyleSheet constructor of the current cache.sheet. This is useful when cache.sheet is not the default implementation. Thanks to that the inner sheet constructed by Global can share the behavior with its "main" sheet that is hold by the cache.

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone Asia/Tokyo, 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 this update 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.

@renovate
renovate Bot requested a review from Hiratake as a code owner March 13, 2022 15:24
@renovate renovate Bot added the 🤖dependencies 依存関係の更新 label Mar 13, 2022
@renovate
renovate Bot force-pushed the renovate/emotion-monorepo branch from ff1aadc to 63d2313 Compare April 1, 2022 04:58
@renovate renovate Bot changed the title fix(deps): update dependency @emotion/react to v11.8.2 fix(deps): update dependency @emotion/react to v11.9.0 Apr 6, 2022
@renovate
renovate Bot force-pushed the renovate/emotion-monorepo branch 2 times, most recently from 9351a67 to f32d13c Compare April 10, 2022 13:01
@renovate
renovate Bot force-pushed the renovate/emotion-monorepo branch from f32d13c to 00c78ab Compare April 23, 2022 12:20
@renovate renovate Bot changed the title fix(deps): update dependency @emotion/react to v11.9.0 fix(deps): update dependency @emotion/react to v11.9.3 Jun 12, 2022
@renovate
renovate Bot force-pushed the renovate/emotion-monorepo branch from 00c78ab to a23c5f2 Compare June 12, 2022 14:26
@renovate
renovate Bot force-pushed the renovate/emotion-monorepo branch from a23c5f2 to 7236054 Compare September 25, 2022 22:29
@renovate renovate Bot changed the title fix(deps): update dependency @emotion/react to v11.9.3 fix(deps): update dependency @emotion/react to v11.10.4 Sep 25, 2022
@renovate
renovate Bot force-pushed the renovate/emotion-monorepo branch from 7236054 to e82ab52 Compare November 20, 2022 16:10
@renovate renovate Bot changed the title fix(deps): update dependency @emotion/react to v11.10.4 fix(deps): update dependency @emotion/react to v11.10.5 Nov 20, 2022
@renovate renovate Bot changed the title fix(deps): update dependency @emotion/react to v11.10.5 fix(deps): update dependency @emotion/react to v11.10.6 Mar 16, 2023
@renovate
renovate Bot force-pushed the renovate/emotion-monorepo branch from e82ab52 to e48dc9d Compare March 16, 2023 06:54
@renovate renovate Bot changed the title fix(deps): update dependency @emotion/react to v11.10.6 fix(deps): update dependency @emotion/react to v11.11.0 May 28, 2023
@renovate
renovate Bot force-pushed the renovate/emotion-monorepo branch from e48dc9d to 491902b Compare May 28, 2023 11:27
@renovate renovate Bot changed the title fix(deps): update dependency @emotion/react to v11.11.0 fix(deps): update dependency @emotion/react to v11.11.1 Jun 7, 2023
@renovate
renovate Bot force-pushed the renovate/emotion-monorepo branch from 491902b to e67c4d4 Compare June 7, 2023 15:12
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

🤖dependencies 依存関係の更新

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants