Nextjs 14 can't run
Answered
Least Tern posted this in #help-forum
Least TernOP
Hello I've recently upgraded to next 14 and started a new project and anytime i try npm run dev i get an issue that tells me that I'm running an older and unsupported version of node which I don't even have installed. (I have node v20). Can someone help me? I've tried using nvm and uninstalling node completley.
62 Replies
if you run
npx next info what does it show (esp node version)also im guessing
node -v shows the v20?Least TernOP
C:\Windows\system32>node --version
v20.11.1
v20.11.1
@riský if you run `npx next info` what does it show (esp node version)
Least TernOP
this is what i get
but when i run the npm run dev
you are using node.js 17.3.0. for next.js, node.js version >= v18.17.0 is required.
you are using node.js 17.3.0. for next.js, node.js version >= v18.17.0 is required.
@riský i was referring to this thing
Least TernOP
i just uninstalled node, now i'm installing it again
then i will run the command
ah ok
i think i have seen this issue before, but i cant remember how it was fixed ðŸ˜
Least TernOP
last time i fixed it by downgrading to next 12
thats a sad fix
Least TernOP
yeah
Least TernOP
i don't want next 12 😦
the command wont even run
npx next infouh
@Least Tern the command wont even run `npx next info`
what does it show?
nothing i suppose
yeah, I mean the error
@riský nothing i suppose
Least TernOP
nothing
blank space
and next dev still broken i guess
Least TernOP
let me try making a new projecty
@Least Tern let me try making a new projecty
also is this windows or linux/macos
Least TernOP
windows
10
nice
can you run
where node and see if the top path is the correct one with your installLeast TernOP
yes
and is there any others there that may be the older version
Least TernOP
C:\Program Files\nodejs\node.exe
i really wonder where next is getting its node from
Least TernOP
me too
i deleted every folder of node
and even in registry
still can't run the new project?
Least TernOP
I can create new project
but it won't start
i just created another one
just in case the other one is corrupted
hmm, same result/error?
last thing, is
node --print "process.versions.node" correct (this is what the next uses to get it)... but there has to be someting more brokenfor example deleting node_modules and npm cache like
npm config get cache.... but i cant see how that would fix itLeast TernOP
it randomly started workin 💀
yay
Least TernOP
PS C:\Users\matij\OneDrive\Desktop\matija programiranje\asdasd> npm run dev
â–² Next.js 14.1.4
- Local: http://localhost:3000
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
asdasd@0.1.0 dev
next dev
â–² Next.js 14.1.4
- Local: http://localhost:3000
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
yay
i don't know what i just did
but it started working
Least TernOP
i deleted some files in temp
and it started working for some reason
@Least Tern but it started working
thats all that matters, that random do things and it works :)
Answer
Least TernOP
finally i can be antisocial again
thank you soo much â¤ï¸
as... poor storage space with node_modules and it really slows down everything
just disable it imo
thats what i do
i just see it too often actually enabled that i have to tell others do remove when i see it