brew no longer willing to continue supporting versions 4.113.0 and later

Open

#7,758 opened on Apr 16, 2026 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 50/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: typescript, vscode
Domain: devtools

Research direction

Start by reproducing the browser activation failure in code-server 4.114.0 and inspect the vscode.git extension at lib/vscode/extensions/git/dist/main.js, along with the extension host path shown in the log. Check why @vscode/fs-copyfile cannot be resolved in this build. Done means the vscode.git extension activates normally and Git visualization works in the browser.

Written by the indexing model from the issue text.

Description

chore code-server

Is there an existing issue for this?

I have searched the existing issues

OS/Web Information

2026-04-16 17:29:41.525 [error] [Window] Activating extension 'vscode.git' failed: Cannot find module '@vscode/fs-copyfile'
Require stack:
- /opt/homebrew/Cellar/code-server/4.114.0/libexec/lib/vscode/extensions/git/dist/main.js
- /opt/homebrew/Cellar/code-server/4.114.0/libexec/lib/vscode/out/vs/workbench/api/node/extensionHostProcess.js.

coder-server version 4.114.0

Steps to Reproduce

Open code-server in any Browser
The git version control visualization is not working.

Expected

Activating extension 'vscode.git' normally

Actual

missing the vscode.git extension's module

Logs

2026-04-16 17:29:41.525 [error] [Window] Activating extension 'vscode.git' failed: Cannot find module '@vscode/fs-copyfile'
Require stack:
- /opt/homebrew/Cellar/code-server/4.114.0/libexec/lib/vscode/extensions/git/dist/main.js
- /opt/homebrew/Cellar/code-server/4.114.0/libexec/lib/vscode/out/vs/workbench/api/node/extensionHostProcess.js.

Screenshot/Video

No response

Does this bug reproduce in native VS Code?

No, this works as expected in native VS Code

Does this bug reproduce in VS Code web?

I did not test VS Code web

Does this bug reproduce in GitHub Codespaces?

I did not test GitHub Codespaces

Are you accessing code-server over a secure context?

I am using a secure context.

Notes