nextjs - 💡(How to fix) Fix VSCodium not detected on macOS when clicking error overlay links [1 pull requests]

Link to the code that reproduces this issue

https://github.com/pipe1os/nextjs-vscodium-repro

To Reproduce

Note: This must be reproduced on a macOS machine with VSCodium installed.

1. Clone the linked minimal reproduction repository and install dependencies.
2. Start the application in development mode (npm run dev).
3. Open http://localhost:3000 in your browser.
4. A deliberate runtime error will appear on the screen (triggered in page.tsx).
5. Click the file path link inside the Next.js error overlay.

Current vs. Expected behavior

Current behavior: When clicking the error link on macOS, VSCodium either fails to launch entirely (because guessEditor is looking for the old Electron binary path), or if it does launch, it fails to navigate to the correct line and column (because the codium switch case is missing in getArgumentsForLineNumber).

Expected behavior: Clicking the file link in the Next.js error overlay should detect VSCodium, launch the editor, and route directly to the line and column of the error.

Provide environment information

**NOTE: I am submitting this from a non-macOS environment, but the bug being reported is strictly isolated to macOS devtools behavior.**

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Fri, 15 May 2026 18:31:42 +0000
  Available memory (MB): 15784
  Available CPU cores: 12
Binaries:
  Node: 24.15.0
  npm: 11.12.1
  Yarn: N/A
  pnpm: 11.1.2
Relevant Packages:
  next: 16.3.0-canary.28 // Latest available version is detected (16.3.0-canary.28).
  eslint-config-next: N/A
  react: 19.2.6
  react-dom: 19.2.6
  typescript: 5.9.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Error Overlay

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

I discovered this bug via codebase analysis and have written a fix with passing unit tests. However, I am currently on Linux and cannot manually test the VSCodium integration on a physical Mac. Could a macOS user clone the linked reproduction to verify this behavior?