Add test:local npm script for running tests from inside VS Code#35
Merged
Conversation
When tests are run from VS Code's integrated terminal, ELECTRON_RUN_AS_NODE=1
leaks from the extension host into the environment, forcing the downloaded
test copy of VS Code to launch as plain Node and reject all its Electron/
Chromium flags ("bad option: --no-sandbox"). Unset that (and the VS Code IPC
vars) so the test instance launches cleanly. Plain `npm test` remains the
cross-platform/CI entry point.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Fab-Cat
approved these changes
May 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a
test:localnpm script that makesnpm testrunnable from VS Code's integrated terminal (and Claude Code).Why
When tests are launched from inside the VS Code extension host,
ELECTRON_RUN_AS_NODE=1leaks into the shell environment. That forces the downloaded test copy of VS Code's Electron binary to run as plain Node, which then rejects every Electron/Chromium launch flag withbad option: --no-sandboxand aborts the run (exit code 9).Unsetting
ELECTRON_RUN_AS_NODE(plus theVSCODE_IPC_HOOK/VSCODE_PIDvars, so the spawned instance doesn't try to attach to the running editor) lets the test instance launch cleanly:Notes
env -uis POSIX, sotest:localtargets macOS/Linux local runs.npm testis unchanged and remains the cross-platform / CI entry point — the variable isn't set in CI, so it already works there.🤖 Generated with Claude Code