Skip to content
This repository was archived by the owner on Sep 27, 2023. It is now read-only.
This repository was archived by the owner on Sep 27, 2023. It is now read-only.

Error installing when using next@canary #23

@logikaljay

Description

@logikaljay

Although this is not a huge deal, because npm i --force.

I am using next@13.4.2-canary.2 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: zact@0.0.2
--
npm ERR! Found: next@13.4.2-canary.2
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 zact@0.0.2
npm ERR! node_modules/zact
npm ERR!   zact@"^0.0.2" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: next@13.4.1
npm ERR! node_modules/next
npm ERR!   peer next@"^13.2.5-canary.x" from zact@0.0.2
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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions