Remove bundled @github/copilot from release tarball

Open Beginner friendly
#266 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
shell

Research direction

Read scripts/create_code_editor_tarball.sh, or the equivalent tarball creation script, and trace how node_modules is assembled. Run the packaging process, verify the resulting tarball contains no @github/copilot packages, and confirm the unnecessary artifact size is removed.

Written by the indexing model from the issue text.

Description

Problem

The CE 1.2.0-rc.1 tarball includes @github/copilot* packages in node_modules/ which add 237 MB to the release artifact:

152M  node_modules/@github/copilot-linuxmusl-x64/
82M   node_modules/@github/copilot/
3.0M  node_modules/@github/copilot-sdk/

This was introduced by VS Code 1.119.x's built-in Copilot integration (ref: https://code.visualstudio.com/updates/v1_116).

Since SageMaker Code Editor removes all Copilot-related features for compliance/branding/legal reasons, these dependencies should also be excluded from the tarball.

Impact

  • Conda package size increased from ~50 MB (CE 1.0.13) to ~150 MB (CE 1.2.0-rc.1)
  • The @github/copilot* packages account for nearly all of the increase
  • Unnecessary binary bloat shipped to every SMD customer

Proposed Fix

Exclude @github/copilot* from node_modules/ in the tarball creation script (scripts/create_code_editor_tarball.sh or equivalent).

rm -rf vscode-reh-web-linux-x64/node_modules/@github

Workaround

The conda-forge feedstock can strip it during packaging in build.sh as an interim fix.

Dominant language
Shell
Stars
26
Forks
24
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/code-editor

All issues in aws/code-editor

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.