Failed Vercel deploymnet. (ENOENT: no such file or directory, open '/vercel/path0/.next/next-server.js.nft.json')

[GAZ082]

Hey there. After merging with the latest changes as today (August 18, 2026) i got this error with the Vercel's auto re-deploy: (the error being near the end of the block, stated in the title.)

Thanks!

16:08:51.570 Running build in Washington, D.C., USA (East) – iad1
16:08:51.571 Build machine configuration: 2 cores, 8 GB
16:08:51.671 Cloning github.com/GAZ082/my-spliit-instance (Branch: main, Commit: 5202899)
16:08:51.672 Previous build caches not available.
16:08:52.453 Cloning completed: 781.000ms
16:08:52.827 Running "vercel build"
16:08:52.846 Vercel CLI 59.0.0
16:08:53.035 Warning: Due to "engines": { "node": ">=24" } in your `package.json` file, the Node.js Version defined in your Project Settings ("22.x") will not apply, Node.js Version "24.x" will be used instead. Learn More: https://vercel.link/node-version
16:08:53.036 Warning: Detected "engines": { "node": ">=24" } in your `package.json` that will automatically upgrade when a new major Node.js Version is released. Learn More: https://vercel.link/node-version
16:08:53.053 Installing dependencies...
16:08:57.495 npm warn deprecated whatwg-encoding@3.1.1: Use @exodus/bytes instead for a more spec-conformant and faster implementation
16:08:58.228 npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
16:08:59.692 npm warn deprecated glob@7.2.3: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
16:09:03.981 npm warn deprecated glob@10.5.0: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
16:09:15.177 
16:09:15.177 > spliit2@0.1.0 postinstall
16:09:15.177 > prisma migrate deploy && prisma generate
16:09:15.177 
16:09:16.048 ◇ injected env (0) from .env // tip: ◈ secrets for agents [www.dotenvx.com]
16:09:16.050 Loaded Prisma config from prisma.config.ts.
16:09:16.051 
16:09:16.174 Prisma schema loaded from prisma/schema.prisma.
16:09:16.177 Datasource "db": PostgreSQL database "verceldb", schema "public" at "ep-dawn-art-a4lkxc7z.us-east-1.aws.neon.tech"
16:09:16.892 
16:09:16.892 25 migrations found in prisma/migrations
16:09:16.892 
16:09:16.995 Applying migration `20260812213708_backfill_original_amount_minor_units`
16:09:17.051 
16:09:17.052 The following migration(s) have been applied:
16:09:17.052 
16:09:17.052 migrations/
16:09:17.052   └─ 20260812213708_backfill_original_amount_minor_units/
16:09:17.052     └─ migration.sql
16:09:17.052 
16:09:17.052 All migrations have been successfully applied.
16:09:17.713 ◇ injected env (0) from .env // tip: ⌘ custom filepath { path: '/custom/path/.env' }
16:09:17.716 Loaded Prisma config from prisma.config.ts.
16:09:17.716 
16:09:17.822 Prisma schema loaded from prisma/schema.prisma.
16:09:18.622 
16:09:18.623 ✔ Generated Prisma Client (7.9.1) to ./src/generated/prisma in 88ms
16:09:18.623 
16:09:18.670 
16:09:18.670 added 1010 packages in 25s
16:09:18.670 
16:09:18.672 223 packages are looking for funding
16:09:18.672   run `npm fund` for details
16:09:18.709 Detected Next.js version: 16.3.1
16:09:18.716 Running "npm run build"
16:09:18.850 
16:09:18.850 > spliit2@0.1.0 build
16:09:18.850 > next build
16:09:18.850 
16:09:19.183 ▲ Next.js 16.3.1 (Turbopack)
16:09:19.375   Applying modifyConfig from Vercel
16:09:19.377 ✓ Running next.config.mjs took 193ms
16:09:19.485 Attention: Next.js now collects completely anonymous telemetry regarding usage.
16:09:19.486 This information is used to shape Next.js' roadmap and prioritize features.
16:09:19.486 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:
16:09:19.486 https://nextjs.org/telemetry
16:09:19.486 
16:09:19.595 - Experiments (use with caution):
16:09:19.597   · serverActions
16:09:19.597 
16:09:19.728   Creating an optimized production build ...
16:09:36.605 ✓ Compiled successfully in 16.0s
16:09:36.617   Running TypeScript ...
16:09:43.550   Finished TypeScript in 6.9s ...
16:09:43.553   Collecting page data using 1 worker ...
16:09:44.292   Generating static pages using 1 worker (0/13) ...
16:09:44.305   Generating static pages using 1 worker (3/13) 
16:09:44.437   Generating static pages using 1 worker (6/13) 
16:09:44.518   Generating static pages using 1 worker (9/13) 
16:09:44.585 ✓ Generating static pages using 1 worker (13/13) in 293ms
16:09:44.593   Finalizing page optimization ...
16:09:44.698   Running onBuildComplete from Vercel
16:09:44.732 Warning: Due to "engines": { "node": ">=24" } in your `package.json` file, the Node.js Version defined in your Project Settings ("22.x") will not apply, Node.js Version "24.x" will be used instead. Learn More: https://vercel.link/node-version
16:09:44.732 Warning: Detected "engines": { "node": ">=24" } in your `package.json` that will automatically upgrade when a new major Node.js Version is released. Learn More: https://vercel.link/node-version
16:09:45.949 
16:09:45.950 > Build error occurred
16:09:45.952 Error: ENOENT: no such file or directory, open '/vercel/path0/.next/next-server.js.nft.json'
16:09:45.953     at ignore-listed frames {
16:09:45.953   errno: -2,
16:09:45.953   code: 'ENOENT',
16:09:45.953   syscall: 'open',
16:09:45.953   path: '/vercel/path0/.next/next-server.js.nft.json'
16:09:45.953 }
16:09:46.027 Error: Command "npm run build" exited with 1