Next.js version 14.2.3 modified the binary, causing deployment issues
Answered
American black bear posted this in #help-forum
American black bearOP
Version 14.2.3 modified the Next.js binary, and now I can't deploy my app.
I have an app running on version 14.1.3. When I wanted to host it, I just had to change the "defaultCommand" from "dev" to "start". However, since version 14.2.3 changed the Next.js binary (located in node_modules/.bin/next), I don't know how to make it work
I have an app running on version 14.1.3. When I wanted to host it, I just had to change the "defaultCommand" from "dev" to "start". However, since version 14.2.3 changed the Next.js binary (located in node_modules/.bin/next), I don't know how to make it work
Answered by joulev
Yeah pinning version is a good idea. Monkey patching things is never a good idea since it can break at any version upgrades, not necessarily major version upgrades
5 Replies
why not run
next start instead of monkey patching the binary?American black bearOP
Well, since my server needs an application startup file (I'm running it in Plesk), that was the best way to make it work without creating any reverse proxy or so
@American black bear Well, since my server needs an application startup file (I'm running it in Plesk), that was the best way to make it work without creating any reverse proxy or so
then maybe make a
and use that
start.sh something like#!/bin/bash
node_modules/.bin/next startand use that
start.sh as the startup fileAmerican black bearOP
Great idea, but it doesn't work. I even tried with the official
server.js file which Vercel shows in the documentation. I guess I'll just downgrade the project to 14.1 and keep using the same config.Yeah pinning version is a good idea. Monkey patching things is never a good idea since it can break at any version upgrades, not necessarily major version upgrades
Answer