Use tree shaking tool to identify dead code in microsoft/vscode

[joyceerhl]

@rebornix mentioned that we have a tree shaking tool for the Monaco editor. This issue tracks adapting the tree shaking tool to identify dead code in the microsoft/vscode repo (unlike in the Monaco editor case, dead code in the microsoft/vscode repo should simply be removed). This could give us more precise dead code results than the ts-unused exports tool.

We could probably add a CI job that runs this tool whenever a new release branch is cut and files issues for debt week, in order to avoid paying the cost of running the tool on every commit.

[VSCodeTriageBot]

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!

[jrieken]

out-of-scope but there will be a future with ESM and that enables built tools that come with module-level tree shaking