Merged
Conversation
Disable npm progress output for the VS Code extension, flatten nested npm script wrappers, and move test preparation into reusable helper scripts. Run compiled node unit tests sequentially so npm run test:node exits cleanly on this Windows environment instead of hanging behind the wildcard runner. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
1 participant
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.
This fixes the Windows-side hang we were seeing around the VS Code extension npm workflows. The underlying issue was not the unit tests themselves - the compiled test files pass - but the way the npm scripts combined nested
npm run ...wrappers, inline shell snippets, npm progress UI, and a single wildcardnode --testinvocation.The change makes the npm path more predictable and non-interactive:
vscode-extension/.npmrccompile,package,pretest, andtest:nodescript chains so they invoke the real commands directly instead of nesting more npm wrappersscripts/prepare-test-output.jshelper instead of an inlinenode -efragmentscripts/run-node-unit-tests.js, emitting compact per-file PASS output and only dumping full child output on failureThe important behavior change is that
npm ci,npm run compile, andnpm run test:nodenow return cleanly in this environment instead of leaving the shell session looking stuck after the actual work has finished.I left the coverage scripts on the existing single-process Node coverage path, aside from sharing the same test-output preparation step, because their behavior is tied to Node's coverage flags and this PR is focused on fixing the hanging standard workflow.