search

vercel / analytics

Privacy-friendly, real-time traffic insights
https://vercel.com/analytics
Mozilla Public License 2.0
416 stars 24 forks source link

Cannot install the latest version of `@vercel/analytics` with `next@14.1.1-canary.78` #136

Closed jayan-blutui closed 5 months ago

jayan-blutui commented 5 months ago

I am currently facing an issue where I cannot install the latest version of @vercel/analytics with any next@14.1.1-canary.* build.

The error message:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @vercel/analytics@1.2.2
npm ERR! Found: next@14.1.1-canary.78
npm ERR! node_modules/next
npm ERR!   next@"^14.1.1-canary.78" from the root project
npm ERR!   peer next@"*" from @markdoc/next.js@0.3.7
npm ERR!   node_modules/@markdoc/next.js
npm ERR!     @markdoc/next.js@"^0.3.7" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional next@">= 13" from @vercel/analytics@1.2.2
npm ERR! node_modules/@vercel/analytics
npm ERR!   @vercel/analytics@"^1.1.4" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: next@14.1.0
npm ERR! node_modules/next
npm ERR!   peerOptional next@">= 13" from @vercel/analytics@1.2.2
npm ERR!   node_modules/@vercel/analytics
npm ERR!     @vercel/analytics@"^1.1.4" 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.
App3x commented 5 months ago

same

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: undefined@undefined
npm ERR! Found: next@14.0.4-canary.17
npm ERR! node_modules/next
npm ERR!   next@"14.0.4-canary.17" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer next@">=13.2.0 <15" from geist@1.2.2
npm ERR! node_modules/geist
npm ERR!   geist@"^1.1.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!
npm ERR! For a full report see:
npm ERR! /Users/pex/.npm/_logs/2024-02-29T04_02_19_743Z-eresolve-report.txt
jayan-blutui commented 5 months ago

Fixed with the stable release of Next.js 14.1.1