We had removed the use of node-prune, under the assumption that npm should be doing a prune by default. It's prune doesn't seem to be aggresive enough to keep the package size under the Azure DevOps vsix size limit though, so we've reverted that change in the build pipeline.
We had removed the use of
node-prune, under the assumption that npm should be doing a prune by default. It's prune doesn't seem to be aggresive enough to keep the package size under the Azure DevOps vsix size limit though, so we've reverted that change in the build pipeline.Fixes #243