NickyMeuleman / nicky-blog

https://nickymeuleman.netlify.app/
14 stars 6 forks source link

fix(deps): update dependency xstate to ^4.37.2 - autoclosed #175

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 2 years ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
xstate (source) ^4.33.6 -> ^4.37.2 age adoption passing confidence

Release Notes

statelyai/xstate ### [`v4.37.2`](https://togithub.com/statelyai/xstate/releases/tag/xstate%404.37.2) [Compare Source](https://togithub.com/statelyai/xstate/compare/xstate@4.37.1...xstate@4.37.2) ##### Patch Changes - [#​3972](https://togithub.com/statelyai/xstate/pull/3972) [`2b9583a63`](https://togithub.com/statelyai/xstate/commit/2b9583a63c9089103365bad9419bd4a1edd43556) Thanks [@​Andarist](https://togithub.com/Andarist)! - The "Some implementations missing" type-level error will now mention what implementations are missing. ### [`v4.37.1`](https://togithub.com/statelyai/xstate/releases/tag/xstate%404.37.1) [Compare Source](https://togithub.com/statelyai/xstate/compare/xstate@4.37.0...xstate@4.37.1) ##### Patch Changes - [#​3913](https://togithub.com/statelyai/xstate/pull/3913) [`1c1874657`](https://togithub.com/statelyai/xstate/commit/1c187465797cd687f311d5a2e18c91738d17f194) Thanks [@​Andarist](https://togithub.com/Andarist)! - Fixed `forwardTo`, `escalate` and `sendUpdate` to be compatible with required action types ### [`v4.37.0`](https://togithub.com/statelyai/xstate/releases/tag/xstate%404.37.0) [Compare Source](https://togithub.com/statelyai/xstate/compare/xstate@4.36.0...xstate@4.37.0) ##### Minor Changes - [#​3835](https://togithub.com/statelyai/xstate/pull/3835) [`431472082`](https://togithub.com/statelyai/xstate/commit/431472082f8b644da9f519931207aa994052517f) Thanks [@​with-heart](https://togithub.com/with-heart)! - The new `TagsFrom` helper type extracts the type of `tags` from a state machine when typegen is enabled: ```ts const machine = createMachine({ // `tags` attached to machine via typegen tsTypes: {} as import('./machine.typegen').Typegen0, tags: ['a', 'b'], states: { idle: { tags: 'c' } } }); type Tags = TagsFrom; // 'a' | 'b' | 'c' ``` If typegen is not enabled, `TagsFrom` returns `string`: ```ts const machine = createMachine({ tags: ['a', 'b'], states: { idle: { tags: 'c' } } }); type Tags = TagsFrom; // string ``` ##### Patch Changes - [#​3855](https://togithub.com/statelyai/xstate/pull/3855) [`02012c2be`](https://togithub.com/statelyai/xstate/commit/02012c2be12f89aac43479b30571688496d8f1b3) Thanks [@​Andarist](https://togithub.com/Andarist)! - Fixed event type narrowing in some of the builtin actions. ### [`v4.36.0`](https://togithub.com/statelyai/xstate/releases/tag/xstate%404.36.0) [Compare Source](https://togithub.com/statelyai/xstate/compare/xstate@4.35.4...xstate@4.36.0) ##### Minor Changes - [#​3393](https://togithub.com/statelyai/xstate/pull/3393) [`430986cdf`](https://togithub.com/statelyai/xstate/commit/430986cdf9ae6919abc9219caeabbf695e96895a) Thanks [@​davidkpiano](https://togithub.com/davidkpiano)! - Deprecated `send()` action creator. Instead of that, you can use `sendTo()` to send events to other actors and `raise()` to send events to the "self" actor. - [#​3802](https://togithub.com/statelyai/xstate/pull/3802) [`8743ad0bd`](https://togithub.com/statelyai/xstate/commit/8743ad0bd6683029a17bec7e1c163ee9a221a276) Thanks [@​Andarist](https://togithub.com/Andarist)! - Fixed a class of inference problems for our builtin actions (`assign`, `sendTo`, etc). - [#​3694](https://togithub.com/statelyai/xstate/pull/3694) [`fd589055b`](https://togithub.com/statelyai/xstate/commit/fd589055bdd92df91bb354471d17b3cda703658f) Thanks [@​Andarist](https://togithub.com/Andarist)! - All actions received a new generic: `TExpressionEvent`. To type things more correctly and allow TS to infer things better we need to distinguish between all events accepted by a machine (`TEvent`) and the event type that actions are "called" with (`TExpressionEvent`). It's best to rely on type inference so you shouldn't have to specify this generic manually all over the place. ##### Patch Changes - [#​3818](https://togithub.com/statelyai/xstate/pull/3818) [`2d8d84fd8`](https://togithub.com/statelyai/xstate/commit/2d8d84fd839b520d73653dba9eba93c9c1cb2249) Thanks [@​Andarist](https://togithub.com/Andarist)! - Fixed inference for `assign` using `PropertyAssigner`, like here: ```ts actions: assign({ counter: 0, delta: (ctx, ev) => ev.delta }); ``` ### [`v4.35.4`](https://togithub.com/statelyai/xstate/releases/tag/xstate%404.35.4) [Compare Source](https://togithub.com/statelyai/xstate/compare/xstate@4.35.3...xstate@4.35.4) ##### Patch Changes - [#​3801](https://togithub.com/statelyai/xstate/pull/3801) [`10d0ba76a`](https://togithub.com/statelyai/xstate/commit/10d0ba76a1e35e7a58d24496caa57da6c28f6c64) Thanks [@​Andarist](https://togithub.com/Andarist)! - Fixed an issue with not clearing registered interpreters when their machines reached final states. ### [`v4.35.3`](https://togithub.com/statelyai/xstate/releases/tag/xstate%404.35.3) [Compare Source](https://togithub.com/statelyai/xstate/compare/xstate@4.35.2...xstate@4.35.3) ##### Patch Changes - [#​3783](https://togithub.com/statelyai/xstate/pull/3783) [`b68f0e8bf`](https://togithub.com/statelyai/xstate/commit/b68f0e8bf0d097f5cb249bd3ddfd5553c1bcc028) Thanks [@​Andarist](https://togithub.com/Andarist)! - Fixed an issue with `EmittedFrom` sometimes not being able to infer the snapshot types from machines. ### [`v4.35.2`](https://togithub.com/statelyai/xstate/releases/tag/xstate%404.35.2) [Compare Source](https://togithub.com/statelyai/xstate/compare/xstate@4.35.1...xstate@4.35.2) ##### Patch Changes - [#​3745](https://togithub.com/statelyai/xstate/pull/3745) [`8cc70d27e`](https://togithub.com/statelyai/xstate/commit/8cc70d27eb927b92603c9643a69351e6168073a6) Thanks [@​viglucci](https://togithub.com/viglucci)! - Fix types to allow for string state name in service onDone/onError config ### [`v4.35.1`](https://togithub.com/statelyai/xstate/releases/tag/xstate%404.35.1) [Compare Source](https://togithub.com/statelyai/xstate/compare/xstate@4.35.0...xstate@4.35.1) ##### Patch Changes - [#​3713](https://togithub.com/statelyai/xstate/pull/3713) [`96052976a`](https://togithub.com/statelyai/xstate/commit/96052976a0d498672b81d1b4e12f589c1e78dfad) Thanks [@​Andarist](https://togithub.com/Andarist)! - Fixed an issue that prevented events sent from the exit actions of the invoking state to be delivered to the invoked actor (when leaving that state). ### [`v4.35.0`](https://togithub.com/statelyai/xstate/releases/tag/xstate%404.35.0) [Compare Source](https://togithub.com/statelyai/xstate/compare/xstate@4.34.0...xstate@4.35.0) ##### Minor Changes - [#​3607](https://togithub.com/statelyai/xstate/pull/3607) [`f95180510`](https://togithub.com/statelyai/xstate/commit/f951805103937205992f52ba7ae84a1b8d6b11c1) Thanks [@​davidkpiano](https://togithub.com/davidkpiano)! - The `createModel(...)` function is now marked as deprecated, as it will be removed in XState version 5. It is recommended to use [Typegen](https://stately.ai/blog/introducing-typescript-typegen-for-xstate) instead. ##### Patch Changes - [#​3677](https://togithub.com/statelyai/xstate/pull/3677) [`a2ecf97ca`](https://togithub.com/statelyai/xstate/commit/a2ecf97cab7587946e947146c8bc3138393a55bf) Thanks [@​Andarist](https://togithub.com/Andarist)! - Fixed an issue with targeted ancestors not being correctly exited when reented during external transitions. - [#​3623](https://togithub.com/statelyai/xstate/pull/3623) [`163c25562`](https://togithub.com/statelyai/xstate/commit/163c25562db20b335540d1342a38a4a12343a299) Thanks [@​arromeo](https://togithub.com/arromeo)! - Fixed an issue with external transitions targeting ancestor states. In such a case, `entry` actions were incorrectly called on the states between the source state and the target state for states that were not reentered within this transition. - [#​3677](https://togithub.com/statelyai/xstate/pull/3677) [`a2ecf97ca`](https://togithub.com/statelyai/xstate/commit/a2ecf97cab7587946e947146c8bc3138393a55bf) Thanks [@​Andarist](https://togithub.com/Andarist)! - Fixed an issue with the *active* descendants of the targeted ancestor not being correctly reentered during external transitions. - [#​3545](https://togithub.com/statelyai/xstate/pull/3545) [`b9995f0`](https://togithub.com/statelyai/xstate/commit/b9995f0844bbbff0c813fee020935dfd7562184b) Thanks [@​with-heart](https://togithub.com/with-heart)! - Updated `pure` action types to allow action `type` strings to be returned in the array. ```ts const machine = createMachine( { entry: ['doStuff'] }, { actions: { doStuff: pure(() => ['someAction']), someAction: () => console.log('executed by doStuff') } } ); ``` Returning action `type` strings were already handled by `xstate` and the types now correctly reflect that. - [#​3666](https://togithub.com/statelyai/xstate/pull/3666) [`5e0808eb4`](https://togithub.com/statelyai/xstate/commit/5e0808eb440f77b8404db6676401849053cfcfd8) Thanks [@​davidkpiano](https://togithub.com/davidkpiano)! - The warning for the `predictableActionArguments` setting has been improved to only warn if it is absent. You can disable the warning by setting `predictableActionArguments: false`. It's still recommended to set it to `true` though. ### [`v4.34.0`](https://togithub.com/statelyai/xstate/releases/tag/xstate%404.34.0) [Compare Source](https://togithub.com/statelyai/xstate/compare/xstate@4.33.6...xstate@4.34.0) ##### Minor Changes - [#​3588](https://togithub.com/statelyai/xstate/pull/3588) [`a4c8ead99`](https://togithub.com/statelyai/xstate/commit/a4c8ead9963f5e9097896ba0fdc1cdcc0acfd621) Thanks [@​davidkpiano](https://togithub.com/davidkpiano)! - The actions `raise` and `sendTo` can now be imported directly from `xstate`: ```js import { raise, sendTo } from 'xstate'; // ... ``` ##### Patch Changes - [#​3599](https://togithub.com/statelyai/xstate/pull/3599) [`333f803f9`](https://togithub.com/statelyai/xstate/commit/333f803f96bae8ecb9a686160c0daca493f9979b) Thanks [@​Andarist](https://togithub.com/Andarist)! - Fixed a regression that has caused `machine.getInitialState(value)` to not follow always transitions correctly.

Configuration

📅 Schedule: Branch creation - "before 9am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

â™» 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.



This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] commented 2 years ago

âš  Artifact update problem

Renovate 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
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @pauliescanlon/gatsby-mdx-embed@0.0.29
npm WARN Found: @mdx-js/react@2.1.5
npm WARN node_modules/@mdx-js/react
npm WARN   @mdx-js/react@"^2.1.5" from the root project
npm WARN   3 more (@nickymeuleman/gatsby-theme-blog, gatsby-plugin-mdx, gatsby-plugin-theme-ui)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @mdx-js/react@"^1.5.3" from @pauliescanlon/gatsby-mdx-embed@0.0.29
npm WARN node_modules/@pauliescanlon/gatsby-mdx-embed
npm WARN   @pauliescanlon/gatsby-mdx-embed@"^0.0.29" from @nickymeuleman/gatsby-theme-blog@3.0.0
npm WARN   node_modules/@nickymeuleman/gatsby-theme-blog
npm WARN 
npm WARN Conflicting peer dependency: @mdx-js/react@1.6.22
npm WARN node_modules/@mdx-js/react
npm WARN   peer @mdx-js/react@"^1.5.3" from @pauliescanlon/gatsby-mdx-embed@0.0.29
npm WARN   node_modules/@pauliescanlon/gatsby-mdx-embed
npm WARN     @pauliescanlon/gatsby-mdx-embed@"^0.0.29" from @nickymeuleman/gatsby-theme-blog@3.0.0
npm WARN     node_modules/@nickymeuleman/gatsby-theme-blog
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @pauliescanlon/gatsby-mdx-embed@0.0.29
npm WARN Found: gatsby@4.24.4
npm WARN node_modules/gatsby
npm WARN   gatsby@"^4.24.4" from the root project
npm WARN   22 more (@nickymeuleman/gatsby-theme-blog, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer gatsby@"^2.18.12" from @pauliescanlon/gatsby-mdx-embed@0.0.29
npm WARN node_modules/@pauliescanlon/gatsby-mdx-embed
npm WARN   @pauliescanlon/gatsby-mdx-embed@"^0.0.29" from @nickymeuleman/gatsby-theme-blog@3.0.0
npm WARN   node_modules/@nickymeuleman/gatsby-theme-blog
npm WARN 
npm WARN Conflicting peer dependency: gatsby@2.32.13
npm WARN node_modules/gatsby
npm WARN   peer gatsby@"^2.18.12" from @pauliescanlon/gatsby-mdx-embed@0.0.29
npm WARN   node_modules/@pauliescanlon/gatsby-mdx-embed
npm WARN     @pauliescanlon/gatsby-mdx-embed@"^0.0.29" from @nickymeuleman/gatsby-theme-blog@3.0.0
npm WARN     node_modules/@nickymeuleman/gatsby-theme-blog
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @pauliescanlon/gatsby-mdx-embed@0.0.29
npm WARN Found: gatsby-plugin-mdx@4.3.0
npm WARN node_modules/gatsby-plugin-mdx
npm WARN   gatsby-plugin-mdx@"^4.3.0" from @nickymeuleman/gatsby-theme-blog@3.0.0
npm WARN   node_modules/@nickymeuleman/gatsby-theme-blog
npm WARN     @nickymeuleman/gatsby-theme-blog@"^3.0.0" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer gatsby-plugin-mdx@"^1.0.64" from @pauliescanlon/gatsby-mdx-embed@0.0.29
npm WARN node_modules/@pauliescanlon/gatsby-mdx-embed
npm WARN   @pauliescanlon/gatsby-mdx-embed@"^0.0.29" from @nickymeuleman/gatsby-theme-blog@3.0.0
npm WARN   node_modules/@nickymeuleman/gatsby-theme-blog
npm WARN 
npm WARN Conflicting peer dependency: gatsby-plugin-mdx@1.10.1
npm WARN node_modules/gatsby-plugin-mdx
npm WARN   peer gatsby-plugin-mdx@"^1.0.64" from @pauliescanlon/gatsby-mdx-embed@0.0.29
npm WARN   node_modules/@pauliescanlon/gatsby-mdx-embed
npm WARN     @pauliescanlon/gatsby-mdx-embed@"^0.0.29" from @nickymeuleman/gatsby-theme-blog@3.0.0
npm WARN     node_modules/@nickymeuleman/gatsby-theme-blog
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @pauliescanlon/gatsby-mdx-embed@0.0.29
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN   react@"^18.2.0" from the root project
npm WARN   29 more (@emotion/react, @emotion/styled, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.12.0" from @pauliescanlon/gatsby-mdx-embed@0.0.29
npm WARN node_modules/@pauliescanlon/gatsby-mdx-embed
npm WARN   @pauliescanlon/gatsby-mdx-embed@"^0.0.29" from @nickymeuleman/gatsby-theme-blog@3.0.0
npm WARN   node_modules/@nickymeuleman/gatsby-theme-blog
npm WARN 
npm WARN Conflicting peer dependency: react@16.14.0
npm WARN node_modules/react
npm WARN   peer react@"^16.12.0" from @pauliescanlon/gatsby-mdx-embed@0.0.29
npm WARN   node_modules/@pauliescanlon/gatsby-mdx-embed
npm WARN     @pauliescanlon/gatsby-mdx-embed@"^0.0.29" from @nickymeuleman/gatsby-theme-blog@3.0.0
npm WARN     node_modules/@nickymeuleman/gatsby-theme-blog
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/auto-id@0.18.0
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN   react@"^18.2.0" from the root project
npm WARN   29 more (@emotion/react, @emotion/styled, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || 17.x" from @reach/auto-id@0.18.0
npm WARN node_modules/@reach/auto-id
npm WARN   @reach/auto-id@"0.18.0" from @reach/tabs@0.18.0
npm WARN   node_modules/@reach/tabs
npm WARN   1 more (@reach/tooltip)
npm WARN 
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN   peer react@"^16.8.0 || 17.x" from @reach/auto-id@0.18.0
npm WARN   node_modules/@reach/auto-id
npm WARN     @reach/auto-id@"0.18.0" from @reach/tabs@0.18.0
npm WARN     node_modules/@reach/tabs
npm WARN     1 more (@reach/tooltip)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/auto-id@0.18.0
npm WARN Found: react-dom@18.2.0
npm WARN node_modules/react-dom
npm WARN   react-dom@"^18.2.0" from the root project
npm WARN   12 more (@gatsbyjs/reach-router, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react-dom@"^16.8.0 || 17.x" from @reach/auto-id@0.18.0
npm WARN node_modules/@reach/auto-id
npm WARN   @reach/auto-id@"0.18.0" from @reach/tabs@0.18.0
npm WARN   node_modules/@reach/tabs
npm WARN   1 more (@reach/tooltip)
npm WARN 
npm WARN Conflicting peer dependency: react-dom@17.0.2
npm WARN node_modules/react-dom
npm WARN   peer react-dom@"^16.8.0 || 17.x" from @reach/auto-id@0.18.0
npm WARN   node_modules/@reach/auto-id
npm WARN     @reach/auto-id@"0.18.0" from @reach/tabs@0.18.0
npm WARN     node_modules/@reach/tabs
npm WARN     1 more (@reach/tooltip)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/descendants@0.18.0
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN   react@"^18.2.0" from the root project
npm WARN   29 more (@emotion/react, @emotion/styled, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || 17.x" from @reach/descendants@0.18.0
npm WARN node_modules/@reach/descendants
npm WARN   @reach/descendants@"0.18.0" from @reach/tabs@0.18.0
npm WARN   node_modules/@reach/tabs
npm WARN 
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN   peer react@"^16.8.0 || 17.x" from @reach/descendants@0.18.0
npm WARN   node_modules/@reach/descendants
npm WARN     @reach/descendants@"0.18.0" from @reach/tabs@0.18.0
npm WARN     node_modules/@reach/tabs
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/descendants@0.18.0
npm WARN Found: react-dom@18.2.0
npm WARN node_modules/react-dom
npm WARN   react-dom@"^18.2.0" from the root project
npm WARN   12 more (@gatsbyjs/reach-router, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react-dom@"^16.8.0 || 17.x" from @reach/descendants@0.18.0
npm WARN node_modules/@reach/descendants
npm WARN   @reach/descendants@"0.18.0" from @reach/tabs@0.18.0
npm WARN   node_modules/@reach/tabs
npm WARN 
npm WARN Conflicting peer dependency: react-dom@17.0.2
npm WARN node_modules/react-dom
npm WARN   peer react-dom@"^16.8.0 || 17.x" from @reach/descendants@0.18.0
npm WARN   node_modules/@reach/descendants
npm WARN     @reach/descendants@"0.18.0" from @reach/tabs@0.18.0
npm WARN     node_modules/@reach/tabs
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/polymorphic@0.18.0
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN   react@"^18.2.0" from the root project
npm WARN   29 more (@emotion/react, @emotion/styled, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || 17.x" from @reach/polymorphic@0.18.0
npm WARN node_modules/@reach/polymorphic
npm WARN   @reach/polymorphic@"0.18.0" from @reach/tabs@0.18.0
npm WARN   node_modules/@reach/tabs
npm WARN   2 more (@reach/tooltip, @reach/visually-hidden)
npm WARN 
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN   peer react@"^16.8.0 || 17.x" from @reach/polymorphic@0.18.0
npm WARN   node_modules/@reach/polymorphic
npm WARN     @reach/polymorphic@"0.18.0" from @reach/tabs@0.18.0
npm WARN     node_modules/@reach/tabs
npm WARN     2 more (@reach/tooltip, @reach/visually-hidden)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/portal@0.18.0
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN   react@"^18.2.0" from the root project
npm WARN   29 more (@emotion/react, @emotion/styled, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || 17.x" from @reach/portal@0.18.0
npm WARN node_modules/@reach/portal
npm WARN   @reach/portal@"0.18.0" from @reach/tooltip@0.18.0
npm WARN   node_modules/@reach/tooltip
npm WARN 
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN   peer react@"^16.8.0 || 17.x" from @reach/portal@0.18.0
npm WARN   node_modules/@reach/portal
npm WARN     @reach/portal@"0.18.0" from @reach/tooltip@0.18.0
npm WARN     node_modules/@reach/tooltip
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/portal@0.18.0
npm WARN Found: react-dom@18.2.0
npm WARN node_modules/react-dom
npm WARN   react-dom@"^18.2.0" from the root project
npm WARN   12 more (@gatsbyjs/reach-router, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react-dom@"^16.8.0 || 17.x" from @reach/portal@0.18.0
npm WARN node_modules/@reach/portal
npm WARN   @reach/portal@"0.18.0" from @reach/tooltip@0.18.0
npm WARN   node_modules/@reach/tooltip
npm WARN 
npm WARN Conflicting peer dependency: react-dom@17.0.2
npm WARN node_modules/react-dom
npm WARN   peer react-dom@"^16.8.0 || 17.x" from @reach/portal@0.18.0
npm WARN   node_modules/@reach/portal
npm WARN     @reach/portal@"0.18.0" from @reach/tooltip@0.18.0
npm WARN     node_modules/@reach/tooltip
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/rect@0.18.0
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN   react@"^18.2.0" from the root project
npm WARN   29 more (@emotion/react, @emotion/styled, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || 17.x" from @reach/rect@0.18.0
npm WARN node_modules/@reach/rect
npm WARN   @reach/rect@"0.18.0" from @reach/tooltip@0.18.0
npm WARN   node_modules/@reach/tooltip
npm WARN 
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN   peer react@"^16.8.0 || 17.x" from @reach/rect@0.18.0
npm WARN   node_modules/@reach/rect
npm WARN     @reach/rect@"0.18.0" from @reach/tooltip@0.18.0
npm WARN     node_modules/@reach/tooltip
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/rect@0.18.0
npm WARN Found: react-dom@18.2.0
npm WARN node_modules/react-dom
npm WARN   react-dom@"^18.2.0" from the root project
npm WARN   12 more (@gatsbyjs/reach-router, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react-dom@"^16.8.0 || 17.x" from @reach/rect@0.18.0
npm WARN node_modules/@reach/rect
npm WARN   @reach/rect@"0.18.0" from @reach/tooltip@0.18.0
npm WARN   node_modules/@reach/tooltip
npm WARN 
npm WARN Conflicting peer dependency: react-dom@17.0.2
npm WARN node_modules/react-dom
npm WARN   peer react-dom@"^16.8.0 || 17.x" from @reach/rect@0.18.0
npm WARN   node_modules/@reach/rect
npm WARN     @reach/rect@"0.18.0" from @reach/tooltip@0.18.0
npm WARN     node_modules/@reach/tooltip
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @reach/tabs@0.18.0
npm ERR! Found: react@18.2.0
npm ERR! node_modules/react
npm ERR!   react@"^18.2.0" from the root project
npm ERR!   peer react@">=16.8.0" from @emotion/react@11.10.4
npm ERR!   node_modules/@emotion/react
npm ERR!     @emotion/react@"^11.10.4" from the root project
npm ERR!     peer @emotion/react@"^11.0.0-rc.0" from @emotion/styled@11.10.4
npm ERR!     node_modules/@emotion/styled
npm ERR!       @emotion/styled@"^11.8.1" from @nickymeuleman/gatsby-theme-blog@3.0.0
npm ERR!       node_modules/@nickymeuleman/gatsby-theme-blog
npm ERR!         @nickymeuleman/gatsby-theme-blog@"^3.0.0" from the root project
npm ERR!     9 more (@nickymeuleman/gatsby-theme-blog, ...)
npm ERR!   28 more (@emotion/styled, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0 || 17.x" from @reach/tabs@0.18.0
npm ERR! node_modules/@reach/tabs
npm ERR!   @reach/tabs@"^0.18.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@17.0.2
npm ERR! node_modules/react
npm ERR!   peer react@"^16.8.0 || 17.x" from @reach/tabs@0.18.0
npm ERR!   node_modules/@reach/tabs
npm ERR!     @reach/tabs@"^0.18.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/worker/9c6c9f/5a2f9d/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/worker/9c6c9f/5a2f9d/cache/others/npm/_logs/2023-06-01T05_36_01_540Z-debug-0.log