This repository was archived by the owner on Jul 16, 2023. It is now read-only.
fix(deps): update emotion monorepo #247
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
10.0.34->10.3.110.0.27->10.3.010.0.31->10.3.010.0.27->10.3.0Release Notes
emotion-js/emotion (@emotion/core)
v10.3.1Compare Source
Patch Changes
33c01578Thanks @Methuselah96! - ExportKeyframestype to avoid TypeScript insertingimport("@​emotion/serialize").Keyframesreferences into declaration files emitted based on a source files exportingkeyframesresult. This avoids issues with strict package managers that don't allow accessing undeclared dependencies.v10.3.0Compare Source
Minor Changes
#2566
122e9f11Thanks @eps1lon, @Andarist! - Fixed hydration mismatches ifReact.useId(an upcoming API in React 18) is used within a tree below our components.#2560
b5a26619Thanks @eps1lon! - Dropped usage of a deprecatedSFCReact type in favor ofFC. TheFCtype has been introduced in@types/[email protected]so this version of this package is now a minimum requirement for TypeScript users.v10.1.1Compare Source
Patch Changes
fe30cbd6#2066 Thanks @Andarist! - Fixed an issue with React giving warning about static children not having unique keys when using the classicjsxfactory. This example illustrates the situation in which this has been incorrectly happening:v10.1.0Compare Source
Minor Changes
71514b06#1970 Thanks @FLGMwt! - Support for the new JSX runtimes has been added. They require compatible React versions and shouldn't be manually used.To use them you can use the new
@jsxImportSource @​emotion/corepragma instead of the old@jsx jsxor you can use@emotion/babel-preset-css-propwith{ runtime: 'automatic' }option to have it handled automatically for you for the whole project.v10.0.35Compare Source
Patch Changes
2cf3b16b#1973 Thanks @santialbo! - Fixed label extraction from the stack traces in node for components wrapped inReact.forwardRef. This has affected only development builds.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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.