Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update emotion monorepo to v11.13.0 #379

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 19, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@emotion/react (source) 11.4.1 -> 11.13.0 age adoption passing confidence
@emotion/styled (source) 11.3.0 -> 11.13.0 age adoption passing confidence

Release Notes

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

v11.13.0

Compare Source

v11.12.0

Compare Source

v11.11.4

Compare Source

Patch Changes
  • #​3159 5b82631d Thanks @​iegik! - Renamed an internal hasOwnProperty to hasOwn. This avoids problems in CommonJS environments when the consumer tries to prevent prototype pollution with Object.freeze(Object.prototype).

v11.11.3

Compare Source

Patch Changes

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.

v11.8.1

Compare Source

Patch Changes
  • #​2651 39ac5b99 Thanks @​Andarist! - Fixed a transpilation issue that caused useInsertionEffect to be referenced directly in the specifiers list of the import statement. This has caused build errors in the consuming tools since the import statement can only reference known exports of a module.

v11.8.0

Compare Source

Minor Changes
  • #​2600 2f27156a Thanks @​Andarist! - Refactored code to use the upcoming React.useInsertionEffect when it's available (this is a new hook that is going to be introduced in React 18). This shouldn't have any effect on existing codebases and the change should be transparent.
Patch Changes
  • #​2609 242f7d8c Thanks @​Andarist! - Added @emotion/babel-plugin as a dependency - this is an actual dependency of the @emotion/react/macro entrypoint and it has to be explicitly declared to fix compatibility with strict package managers.

  • #​2615 3d672acd Thanks @​srmagura! - Fix an edge case where runtime label extraction in class components led to invalid class names in Firefox. This only affected the development build of Emotion.

  • Updated dependencies [2f27156a]:

v11.7.1

Compare Source

Patch Changes
  • #​2577 04681a5f 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.

  • #​2590 1554a7e2 Thanks @​Andarist! - Upgraded and pinned the version of Stylis - the CSS parser that Emotion uses under the hood.

  • Updated dependencies [1554a7e2]:

v11.7.0

Compare Source

Patch Changes
  • #​2534 57be9e8c Thanks @​srmagura! - Changed the implementation of the runtime label extraction in elements using the css prop (that only happens in development) to one that should yield more consistent results across browsers. This fixes some minor issues with React reporting hydration mismatches that wouldn't happen in production.

v11.6.0

Compare Source

Minor Changes
  • #​2542 eb013d25 Thanks @​eps1lon! - Fixed hydration mismatches if React.useId (an upcoming API in React 18) is used within a tree below our components.
Patch Changes

v11.5.0

Compare Source

Patch Changes

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from bf6522d to 4957067 Compare November 14, 2021 08:39
@renovate renovate bot changed the title chore(deps): update dependency @emotion/react to v11.5.0 chore(deps): update emotion monorepo to v11.6.0 Nov 14, 2021
@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from 4957067 to bb18fa9 Compare November 26, 2021 12:18
@renovate renovate bot changed the title chore(deps): update emotion monorepo to v11.6.0 chore(deps): update emotion monorepo Nov 26, 2021
@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from bb18fa9 to 315176c Compare December 12, 2021 23:39
@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from 315176c to 90007ed Compare March 7, 2022 15:51
@renovate renovate bot changed the title chore(deps): update emotion monorepo chore(deps): update emotion monorepo to v11.8.1 Mar 7, 2022
@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from 90007ed to f48cd70 Compare March 14, 2022 14:32
@renovate renovate bot changed the title chore(deps): update emotion monorepo to v11.8.1 chore(deps): update emotion monorepo Mar 14, 2022
@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from f48cd70 to 15bdd78 Compare April 6, 2022 11:01
@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from 15bdd78 to 68cb293 Compare June 18, 2022 18:11
@renovate renovate bot changed the title chore(deps): update emotion monorepo chore(deps): update emotion monorepo to v11.9.3 Jun 18, 2022
@renovate renovate bot changed the title chore(deps): update emotion monorepo to v11.9.3 chore(deps): update emotion monorepo to v11.10.4 Sep 25, 2022
@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from 17baf37 to ebed0ff Compare November 20, 2022 16:45
@renovate renovate bot changed the title chore(deps): update emotion monorepo to v11.10.4 chore(deps): update emotion monorepo to v11.10.5 Nov 20, 2022
@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from ebed0ff to 4712ed7 Compare March 18, 2023 10:10
@renovate renovate bot changed the title chore(deps): update emotion monorepo to v11.10.5 chore(deps): update emotion monorepo to v11.10.6 Mar 18, 2023
@renovate renovate bot changed the title chore(deps): update emotion monorepo to v11.10.6 chore(deps): update emotion monorepo to v11.11.0 May 28, 2023
@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from 4712ed7 to ccc32ae Compare May 28, 2023 11:11
@renovate renovate bot changed the title chore(deps): update emotion monorepo to v11.11.0 chore(deps): update emotion monorepo Jun 7, 2023
@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from ccc32ae to 07a0a23 Compare June 7, 2023 11:23
@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from 07a0a23 to 12fd0ab Compare December 23, 2023 21:56
@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from 12fd0ab to eb05b39 Compare March 2, 2024 17:37
@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from eb05b39 to 0f003e5 Compare March 29, 2024 20:28
@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from 0f003e5 to a22fc92 Compare July 19, 2024 07:55
@renovate renovate bot changed the title chore(deps): update emotion monorepo chore(deps): update emotion monorepo to v11.12.0 Jul 19, 2024
@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from a22fc92 to 3a150ce Compare July 20, 2024 07:48
@renovate renovate bot changed the title chore(deps): update emotion monorepo to v11.12.0 chore(deps): update emotion monorepo to v11.13.0 Jul 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants