[NEXT-1017] Intercepted routes: error on Vercel builds only

[alex-ketch]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 21:00:17 PST 2023; root:xnu-8796.101.5~3/RELEASE_X86_64
    Binaries:
      Node: 18.15.0
      npm: 9.5.0
      Yarn: N/A
      pnpm: 8.1.0
    Relevant packages:
      next: 13.3.1-canary.7
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true)

Link to the code that reproduces this issue

https://intercepted-modals.vercel.app

To Reproduce

Clone and deploy the following project to Vercel: https://github.com/alex-ketch/intercepted-modals.
An existing deployment can be seen here: https://intercepted-modals.vercel.app

404 Error:

• Open https://intercepted-modals.vercel.app
• Click "intercepting-parallel-modal" link
• Click on any of the links listed under "Feed for userId"
• See 404 error
• Refresh the page. Content of photo detail page is present.

500 Error:

• Open https://intercepted-modals.vercel.app
• Click "dynamic-sibling-route" link
• Click on any of the links listed under "Feed for userId"
• See 500 error
• Refresh the page. 500 error is still present.

Describe the Bug

When a project using intercepted routes is deployed to Vercel, a runtime error is encountered when attempting to open the intercepted route. What makes it hard to debug is that this error is not present during local development builds, or vercel dev commands.

There are two similar scenarios which both cause errors:

• 404 error for an intercepted route for a different path segment (e.g. from /intercepting-parallel-modal/userId intercepting intercepting-parallel-modal/photo/1)
• 500 error for intercepted route for a the current path segment (e.g. from dynamic-sibling-route intercepting /dynamic-sibling-route/3)

The above linked reproduction repo is directly based on the e2e tests found here: https://github.com/vercel/next.js/tree/canary/test/e2e/app-dir/parallel-routes-and-interception/app/(group). I've added another use case of catching a dynamic path for the current path under the dynamic-sibling-route folder.

When attempting to visit the modal route a 404 error is shown, but no relevant logs are seen in Vercel.
When attempting to visit a route for a dynamic sibling route the following 500 error is logged.

Error: Cannot find module '/var/task/.next/server/app/(group)/dynamic-sibling-route/@modal/(.)/[id]/page.js'
Require stack:
- /var/task/node_modules/next/dist/server/require.js
- /var/task/node_modules/next/dist/server/next-server.js
- /var/task/___next_launcher.cjs
    at Module._resolveFilename (node:internal/modules/cjs/loader:1039:15)
    at mod._resolveFilename (/var/task/node_modules/next/dist/build/webpack/require-hook.js:23:32)
    at Module._load (node:internal/modules/cjs/loader:885:27)
    at Module.require (node:internal/modules/cjs/loader:1105:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at Object.requirePage (/var/task/node_modules/next/dist/server/require.js:134:12)
    at /var/task/node_modules/next/dist/server/load-components.js:51:73
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Object.loadComponentsImpl [as loadComponents] (/var/task/node_modules/next/dist/server/load-components.js:51:26)
    at async NextNodeServer.findPageComponentsImpl (/var/task/node_modules/next/dist/server/next-server.js:667:36) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/var/task/node_modules/next/dist/server/require.js',
    '/var/task/node_modules/next/dist/server/next-server.js',
    '/var/task/___next_launcher.cjs'
  ],
  page: '/dynamic-sibling-route/2'
}
RequestId: fda2079e-9e18-4eda-aae7-fea0407cb78b Error: Runtime exited with error: exit status 1
Runtime.ExitError

---

• CodeSandbox: error is not present
  • incidentally the intercepting-parallel-modal example also demonstrates issue with clearing the slot contents as mentioned in Parallel Route - Navigation fails to clear slot  #48124

Thought I'd mentioned you @feedthejim since I noticed you were working on these features recently. Let me know if you need any further info in debugging this.

Expected Behavior

Should match behaviour seen in local development builds.
I.e. clicking on a link for an item in the feed should show contents of the detail view.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

Vercel

_{From SyncLinear.com | NEXT-1017}

[feedthejim]

will look into it

[feedthejim]

@alex-ketch it seems you're using the wrong syntax for intercepting routes. In your project the path is (.)/[id], whereas you should be using (.)[id]. There's a bug for that particular usecase though tracked in #48143

It's definitely curious that it works, will add an error for that.

[feedthejim]

There was also a bug for the 404 issue which I just fixed now @alex-ketch thanks for reporting

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.