You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 27, 2023. It is now read-only.
Although this is not a huge deal, because npm i --force.
I am using [email protected] as it has the fix for server actions that use next/headers and next/cookies.
The previous workaround was to import them in a server component and send them to the client component as props.
npm ERR! While resolving: [email protected]
--
npm ERR! Found: [email protected]
npm ERR! node_modules/next
npm ERR! next@"^13.4.2-canary.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer next@"^13.2.5-canary.x" from [email protected]
npm ERR! node_modules/zact
npm ERR! zact@"^0.0.2" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/next
npm ERR! peer next@"^13.2.5-canary.x" from [email protected]
npm ERR! node_modules/zact
npm ERR! zact@"^0.0.2" from the root project
I am not entirely sure why this is happening as the semver required in the package.json for zact is ^13.3.0 which validates the canary version I am installing (according to random semver checker I found on google): https://jubianchi.github.io/semver-check/#/^13.3.0/13.4.2-canary.2
Maybe someone with better knowledge of semver can explain?
The text was updated successfully, but these errors were encountered:
logikaljay
changed the title
Error when using with next@canary
Error installing when using next@canary
May 9, 2023
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Although this is not a huge deal, because
npm i --force
.I am using
[email protected]
as it has the fix for server actions that usenext/headers
andnext/cookies
.The previous workaround was to import them in a server component and send them to the client component as props.
I am not entirely sure why this is happening as the semver required in the
package.json
forzact
is^13.3.0
which validates the canary version I am installing (according to random semver checker I found on google):https://jubianchi.github.io/semver-check/#/^13.3.0/13.4.2-canary.2
Maybe someone with better knowledge of semver can explain?
The text was updated successfully, but these errors were encountered: