copilot: bump esbuild from 0.25.6 to 0.27.2#309975
Merged
Conversation
The copilot extension was using esbuild 0.25.6 (transitive via tsx), which has a memory leak in long-running watch mode. The esbuild service process grows to 1-2.7 GB over hours of watch usage, while esbuild 0.27.2 (used by vscode's own build) stays at 7-29 MB even after days. Add esbuild 0.27.2 as a direct devDependency so the build script resolves to the fixed version. tsx retains its own nested 0.25.x. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds a direct devDependency on esbuild@0.27.2 for the Copilot extension so the build/watch pipeline uses a newer esbuild version (matching VS Code’s), avoiding the memory growth observed with the transitive esbuild@0.25.x pulled in via tsx.
Changes:
- Add
esbuild: "0.27.2"toextensions/copilotdevDependencies to force module resolution to the newer esbuild.
Show a summary per file
| File | Description |
|---|---|
| extensions/copilot/package.json | Adds a direct esbuild devDependency to ensure the extension build uses esbuild 0.27.2 instead of tsx’s transitive 0.25.x. |
Copilot's findings
Files not reviewed (1)
- extensions/copilot/package-lock.json: Language not supported
- Files reviewed: 1/2 changed files
- Comments generated: 1
Contributor
Screenshot ChangesBase: Changed (1)
|
| Before | After |
|---|---|
 |
 |
Yoyokrazy
approved these changes
Apr 14, 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
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.
Problem
The copilot extension's esbuild service process (
--service=0.25.6 --ping) leaks memory in long-running watch mode, growing to 1–2.7 GB over hours. Meanwhile, vscode's own build uses esbuild 0.27.2, which stays at 7–29 MB even after days.The 0.25.6 version comes as a transitive dependency via
tsx@4.20.3. Since there's no direct esbuild dependency in the copilot extension, the build script (.esbuild.ts) resolves to tsx's copy.Measurement
code/vscodevsc1vsc2Fix
Add
esbuild: "0.27.2"as a direct devDependency. npm nests tsx's own esbuild@0.25.x undernode_modules/tsx/node_modules/esbuild, so tsx continues to work correctly.