Thought I would try the preview version of Next (16.3.0-preview.9 to be specific), and seems it works great, with the exception that I'm getting this error on the build-server:
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @vercel/analytics@2.0.1
npm error Found: next@16.3.0-preview.9
npm error node_modules/next
npm error next@"16.3.0-preview.9" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional next@">= 13" from @vercel/analytics@2.0.1
npm error node_modules/@vercel/analytics
npm error @vercel/analytics@"2.0.1" from the root project
npm error
npm error Conflicting peer dependency: next@16.2.11
npm error node_modules/next
npm error peerOptional next@">= 13" from @vercel/analytics@2.0.1
npm error node_modules/@vercel/analytics
npm error @vercel/analytics@"2.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error C:\Users\torle\AppData\Local\npm-cache\_logs\2026-07-24T23_02_48_171Z-eresolve-report.txt
npm error A complete log of this run can be found in: C:\Users\torle\AppData\Local\npm-cache\_logs\2026-07-24T23_02_48_171Z-debug-0.log
Would be great if [the peer dependency](https://github.com/vercel/analytics/blob/d5df714080cbfdc7ee5e84b9aa6918e291a8e979/packages/web/package.json#L127], which is now "next": ">= 13" could be widened to also include preview versions.
I can work around it by overriding the install command on Vercel to npm i --force, but would prefer if I didn't have to do that.
Thought I would try the preview version of Next (
16.3.0-preview.9to be specific), and seems it works great, with the exception that I'm getting this error on the build-server:Would be great if [the peer dependency](https://github.com/vercel/analytics/blob/d5df714080cbfdc7ee5e84b9aa6918e291a8e979/packages/web/package.json#L127], which is now
"next": ">= 13"could be widened to also include preview versions.I can work around it by overriding the install command on Vercel to
npm i --force, but would prefer if I didn't have to do that.