next.js

dadc154d - fix(devtools): detect VS Code renamed macOS binary in launch-editor (#93971)

fix(devtools): detect VS Code renamed macOS binary in launch-editor (#93971) ### What? Add the new VS Code macOS binary name (`Code`) to the `COMMON_EDITORS_MACOS` detection map in `launch-editor.ts`, alongside the legacy `Electron` entry. Same for VS Code Insiders (`Code - Insiders`). ### Why? VS Code renamed its macOS binary from `Electron` to `Code`. The `guessEditor()` function detects running editors by matching `ps x` output against known process paths. Since the old key (`…/MacOS/Electron`) no longer appears in the process list, VS Code is not detected — the "open in editor" button silently does nothing. ### How? Added two new entries to `COMMON_EDITORS_MACOS` that map the renamed binaries to the same `code` CLI path. The old entries are kept for backward compatibility. <!-- NEXT_JS_LLM_PR -->