🐛 BUG: wrangler pages dev hot reloading error on Next.js local development

[tengweiherr]

Which Cloudflare product(s) does this pertain to?

Pages

What version(s) of the tool(s) are you using?

3.5.0 [Wrangler]

What version of Node are you using?

16.18.1

What operating system are you using?

Mac

Describe the Bug

I was following the local development guide of Next.js on @cloudflare/next-on-pages. The following is the summary:

1. Enable Next.js pages local development in watch mode
   npx @cloudflare/next-on-pages --watch
2. Then in a separate terminal run:
   npx wrangler pages dev .vercel/output/static --compatibility-flag=nodejs_compat

On every change in the directory, it does trigger the build. During every build, the files in .vercel/output will be removed and replaced by updated asset. The building process takes quite some time, resulting in the following error from the wrangler:

✘ [ERROR] Could not validate _routes.json at /Users/wteng/Desktop/web-app/.vercel/output/static: Error: ENOENT: no such file or directory, open '/Users/wteng/Desktop/web-app/.vercel/output/static/_routes.json'

▲ [WARNING] Falling back to the following _routes.json default: {

    "version": 1,
    "include": [
      "/*"
    ],
    "exclude": []
  }

/usr/local/lib/node_modules/wrangler/wrangler-dist/cli.js:30632
            throw a;
            ^

[Error: ENOENT: no such file or directory, scandir '/Users/wteng/Desktop/web-app/.vercel/output/static/_worker.js'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'scandir',
  path: '/Users/wteng/Desktop/web-app/.vercel/output/static/_worker.js'
}

I also tried npx wrangler pages dev --live-reload .vercel/output/static --compatibility-flag=nodejs_compat but still the result.

Expected result

It should work like a proper hot reloading application without error.

Please provide a link to a minimal reproduction

No response

[ln-north]

When a process remains on port 8788, it is not a fundamental solution, but adding lsof -ti:8788 | xargs kill -9; can make development a bit easier.
(For example, lsof -ti:8788 | xargs kill -9; yarn pages:dev or lsof -ti:8788 | xargs kill -9; npx wrangler pages dev ... in package.json)

I hope this issue will be resolved.

[kika]

Are you considering issues for reopening or it's better to file a new one?

This issue is not fixed if being used together with workaround for the issue #3676
The first run of sudo wrangler pages dev --port 443 --live-reload works fine, but after rebuild and reload it bails out with the same unhandled exception as in #3676

[petebacondarwin]

Please create a new one.