Sometimes the bundle fails in vscode because an extraneous dependency (typescript) is require'd, but is not included in the bundle.
This can probably be accomplished with this eslint rule, but the vscode integration tests should 100% be using the bundled version rather than --extensionDevPath.
I think the best that can be done is with daa3f672cbe518b2afb6d96fe424806e4a495360, since vscode's testing framework has no mechanism to test an actual bundle.
Sometimes the bundle fails in vscode because an extraneous dependency (
typescript
) isrequire
'd, but is not included in the bundle.This can probably be accomplished with this
eslint
rule, but the vscode integration tests should 100% be using the bundled version rather than--extensionDevPath
.