fix(deps): update emotion monorepo to v11 (major) #76
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: package-lock.json |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.17->^11.0.0^10.0.17->^11.0.0Release Notes
emotion-js/emotion
v11.0.0Compare Source
Major Changes
b8476e08#1675 Thanks @mitchellhamilton! - Rename@emotion/coreto@emotion/react. Please change any imports of@emotion/coreto import@emotion/reactor use the@emotion/pkg-renamingESLint rule from@emotion/eslint-plugin.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.v10.0.34Compare Source
Patch Changes
4979ebb2#1966 Thanks @chnakamura! - Fixed label extraction from the stack traces in Chrome in certain scenarios. This has affected only development builds.v10.0.28Compare Source
Patch Changes
d0b2a94#1714 Thanks @Andarist! - Fixed label extraction from the stack traces in FireFox and Safari. We have failed to match a label in Emotion wrappers like Theme UI which caused SSR mismatches in mentioned browsers. This has affected only development builds.v10.0.27Compare Source
Patch Changes
4c62ae9#1698 Thanks @Andarist! - Add LICENSE file4c62ae9]:v10.0.22Compare Source
Patch Changes
4fc5657a#1219 Thanks @Andarist! - Add dev hint about css object being stringified by accident2fc75f26#1548 Thanks @Andarist! - Accept objects asclassNamein jsx-created components (they are stringified) to match React behavior10211951#1553 Thanks @Andarist! - Add dev warning about keyframes being interpolated into plain strings.57a767ea#1560 Thanks @Andarist! - Fix composition of styles without a final semicolon in a declaration blockUpdated dependencies [
4fc5657a,10211951,57a767ea,c3f0bc10,11bea3a8]:v10.0.21Compare Source
Patch Changes
/* #__PURE__ */annotation to creation of EmotionCssPropInternalv10.0.20Compare 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.
This PR has been generated by Mend Renovate. View repository job log here.