Dependency problem after upgrading to nextjs 14

[levipadre]

Description

using next-intl@3.0.0-rc.6:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: next-intl@3.0.0-rc.6
npm ERR! Found: next@14.0.0
npm ERR! node_modules/next
npm ERR!   next@"14.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer next@"^10.0.0 || ^11.0.0 || ^12.0.0 || ^13.0.0" from next-intl@3.0.0-rc.6
npm ERR! node_modules/next-intl
npm ERR!   next-intl@"^3.0.0-rc.6" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: next@13.5.6
npm ERR! node_modules/next
npm ERR!   peer next@"^10.0.0 || ^11.0.0 || ^12.0.0 || ^13.0.0" from next-intl@3.0.0-rc.6
npm ERR!   node_modules/next-intl
npm ERR!     next-intl@"^3.0.0-rc.6" 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.

but with next-intl@2.21.0 is the same for me:

npm ERR! code ETARGET
npm ERR! notarget No matching version found for next-intl@^3.0.0-rc.19.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! A complete log of this run can be found in: /Users/leventekosa/.npm/_logs/2023-10-27T07_58_57_661Z-debug-0.log
leventekosa@Leventes-iMac-3 ciwf-frontend-application % npm i
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: ciwf-frontend-application@0.1.0
npm ERR! Found: next@14.0.0
npm ERR! node_modules/next
npm ERR!   next@"14.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer next@"^10.0.0 || ^11.0.0 || ^12.0.0 || ^13.0.0" from next-intl@2.21.0
npm ERR! node_modules/next-intl
npm ERR!   next-intl@"^2.21.0" from the root project

Any suggestion?

Mandatory reproduction URL (CodeSandbox or GitHub repository)

app directory

Reproduction description

Steps to reproduce:

1. update to nextjs 14

Expected behaviour

Maybe just needs to adjust next intl to v14.

[dantecarlo]

It is also happening with 3.0.0-beta.19

[amannn]

Please see #584 (comment), seems like this was a duplicate.