Intercepting Routes with Catch-all Segments broken

[nowlena]

Verify canary release

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

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Fri Jan 27 02:56:13 UTC 2023
Binaries:
  Node: 18.16.0
  npm: 9.5.1
  Yarn: N/A
  pnpm: 8.6.3
Relevant Packages:
  next: 13.4.8-canary.2
  eslint-config-next: 13.4.7
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A

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

App directory (appDir: true), Routing (next/router, next/navigation, next/link)

Link to the code that reproduces this issue or a replay of the bug

/~https://github.com/vercel-labs/nextgram

To Reproduce

It looks as though the pathing is broken when trying to use Catch-all Segments with Intercepting routes.

• works: /(.)photo/[id]
• breaks: /(.)photo/[...id]

Describe the Bug

The error that I receive is:

/node_modules/next/dist/compiled/path-to-regexp/index.js:47
    throw new TypeError("Missing parameter name at " + i);

TypeError: Missing parameter name at 9
    at lexer (/next/dist/compiled/path-to-regexp/index.js:47:23)
    at parse (/next/dist/compiled/path-to-regexp/index.js:97:18)
    at stringToRegexp (/next/dist/compiled/path-to-regexp/index.js:329:27)
    at pathToRegexp (/next/dist/compiled/path-to-regexp/index.js:403:12)
    at getPathMatch (/next/dist/shared/lib/router/utils/path-match.js:14:51)
    at getCustomRoute (/next/dist/server/server-route-utils.js:40:47)
    at buildRewrite (/next/dist/server/next-server.js:1408:75)
    at /next/dist/server/next-server.js:1476:79
    at Array.map (<anonymous>)
    at DevServer.generateRewrites (/next/dist/server/next-server.js:1476:70)
    at Watchpack.<anonymous> (/next/dist/server/dev/next-dev-server.js:576:50)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

note: I've shortened the paths to node_modules above

Expected Behavior

I'd expect this intercepting routes to work properly with catch-all segments

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[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.