microsoft / microsoft/vscode-edge-devtools
bundle extension output to reduce shipped file count (~10.6k files)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 827
- Forks
- 358
- Avg merge
- 20h 32m
- Merged PRs (30d)
- 10
Description
Environment (please complete the following information):
- OS (e.g., Windows 10): Windows 11
- Extension version (e.g., 1.2.3): (hover "Microsoft Edge Tools for VS Code" in Extensions panel)
Describe the bug:
Extension ships ~10,600 files. Mostly unbundled node_modules. Bad for NTFS, slow to install, hurts VS Code startup. VS Code says bundle your extension.
Repro steps:
- Go to
%USERPROFILE%\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-* - Run
(Get-ChildItem -Recurse | Measure-Object).Count - See ~10,600 files
Expected behavior:
Use webpack or esbuild. Ship handful of files. Pylance and ESLint do it. Under 200 files each.
Additional context:
No other context.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No specific files or tests are named. Inspect the extension's build and packaging configuration, reproduce the installed file count from the issue, and determine the current entry points and dependencies being shipped. Done means the extension still works while shipping a substantially smaller set of files, ideally under 200 as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, webpack
- Domain
- build-system, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100