Updating to Next.js 14.2.16: Should I Update React, React-DOM, and ESLint Config?
Unanswered
Yellow croaker posted this in #help-forum
Yellow croakerOP
Hello, I would like to update my project to the latest Next.js 14 version. It seems that running npm i next@14.2.16 should work, because if I use npm i next@latest react@latest react-dom@latest eslint-config-next@latest, I think that would upgrade me to Next.js 15. Would updating to 14.2.16 be enough without updating eslint-config-next, react-dom, or react? I’m currently running Next.js 14.0.
9 Replies
Yellow croakerOP
Any insight to this?
@Yellow croaker Hello, I would like to update my project to the latest Next.js 14 version. It seems that running npm i next@14.2.16 should work, because if I use npm i next@latest react@latest react-dom@latest eslint-config-next@latest, I think that would upgrade me to Next.js 15. Would updating to 14.2.16 be enough without updating eslint-config-next, react-dom, or react? I’m currently running Next.js 14.0.
Giant panda
Hi, did you ever come to a conclusion? I want to update from v14.2.3 to v14.2.21 and also wondering about the peer dependencies.
@Yellow croaker @Giant panda react should remain at 18.3.1. eslint-config-next should also be at v14, at the same version as next
in this particular case i would just edit the version number inside package.json to the new version and then rerun the install command of the package manager you use
in this particular case i would just edit the version number inside package.json to the new version and then rerun the install command of the package manager you use
@joulev <@309224493509771265> <@683539537854857224> react should remain at 18.3.1. eslint-config-next should also be at v14, at the same version as next
in this particular case i would just edit the version number inside package.json to the new version and then rerun the install command of the package manager you use
Giant panda
How about running
pnpm up next@14.2.22?@Giant panda How about running `pnpm up next@14.2.22`?
I never used pnpm up so I’m not sure, but as long as the versions match (next 14-react 18, or next 15-react 19), it’ll work
@joulev I never used pnpm up so I’m not sure, but as long as the versions match (next 14-react 18, or next 15-react 19), it’ll work
Giant panda
Is it a good idea to update to the latest minor version of
In the nextjs docs, they give this command for upgrading from 13 to 14:
Though am I misunderstanding how it works? If I ran
react, react-dom, eslint-config-next? Is there a convenient way to update them all within the version boundary of current nextjs installed (14.2.22)?In the nextjs docs, they give this command for upgrading from 13 to 14:
npm i next@next-14 react@latest react-dom@latest && npm i eslint-config-next@next-14 -DThough am I misunderstanding how it works? If I ran
npm i react@latest react-dom@latest eslint-config-next@latest, is that going to keep me within the safe boundary of my NextJS 14 version or go too high in version?Perhaps I should do something like
pnpm up react@^18 react-dom@^18 eslint-config-next@14.2.22?@Giant panda Is it a good idea to update to the latest minor version of `react`, `react-dom`, `eslint-config-next`? Is there a convenient way to update them all within the version boundary of current nextjs installed (14.2.22)?
In the nextjs docs, they give this command for upgrading from 13 to 14:
npm i next@next-14 react@latest react-dom@latest && npm i eslint-config-next@next-14 -D
Though am I misunderstanding how it works? If I ran `npm i react@latest react-dom@latest eslint-config-next@latest`, is that going to keep me within the safe boundary of my NextJS 14 version or go too high in version?
back then the command was correct because back then react 18 was at latest, now it is 19 so that command is no longer corect