Error when deploy it to Vercel "No such file or directory"

[xaldiy]

Bug report

• Version: 0.7.1
• URL: No
• Repository: Yes

Description

[15:05:35.411] Running build in Washington, D.C., USA (East) – iad1
[15:05:35.611] Cloning github.com/DiamondTrack/the-aldi (Branch: main, Commit: bda78d4)
[15:05:35.639] Skipping build cache, deployment was triggered without cache.
[15:05:43.575] Cloning completed: 7.964s
[15:05:44.059] Running "vercel build"
[15:05:44.509] Vercel CLI 34.2.8
[15:05:45.374] > Installing Builder: vercel-php@0.7.0
[15:05:48.570] 🐘 Downloading user files
[15:05:48.571] 🐘 Downloading PHP runtime files
[15:05:48.573] 🐘 Installing Composer dependencies [START]
[15:05:48.854] php: error while loading shared libraries: libssl.so.10: cannot open shared object file: No such file or directory
[15:05:48.856] Error: Exited with 127
[15:05:48.857] at ChildProcess. (/vercel/path0/.vercel/builders/node_modules/vercel-php/dist/utils.js:182:24)
[15:05:48.857] at ChildProcess.emit (node:events:518:28)
[15:05:48.857] at ChildProcess.emit (node:domain:488:12)
[15:05:48.857] at ChildProcess._handle.onexit (node:internal/child_process:294:12)
[15:05:48.885] Error: Command "vercel build" exited with 1
[15:05:48.955] Command "vercel build" exited with 1
[15:05:48.990]

[BintangDeveloper]

Had the same problem as mine, but still no solution.

[oregdesign]

try this..
in your project dashboard go to,
setting > general > node.js version ( change to 18x ) and hit the "save" button
and redeploy.

[maverickdude]

I'm having this issue as well.

[dextermb]

try this.. in your project dashboard go to, setting > general > node.js version ( change to 18x ) and hit the "save" button and redeploy.

Downgrading from Node 20 to 18 seems to resolve my issue for now.

[FojoBass]

try this.. in your project dashboard go to, setting > general > node.js version ( change to 18x ) and hit the "save" button and redeploy.

Downgrading from Node 20 to 18 seems to resolve my issue for now.

But how? I can't seem to locate the "node.js version" option in my settings.

[f3l1x]

Hi, can you test latest version 0.7.3 (at this moment)?

[tao]

I ran into the same issue with v0.7.3

After specifying the node version in package.json the errors disappeared.

  "engines": {
    "node": "18.x"
  },