Use tree shaking tool to identify dead code in microsoft/vscode
#165092
Labels
engineering
VS Code - Build / issue tracking / etc.
feature-request
Request for new features or functionality
*out-of-scope
Posted issue is not in scope of VS Code
Milestone
@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 themicrosoft/vscode
repo should simply be removed). This could give us more precise dead code results than thets-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.
The text was updated successfully, but these errors were encountered: