Test for #71048 - [x] Mac @Tyriar - [x] Linux @aeschli - [x] Windows @bpasero Complexity: 2 Overview: `vscode` has been split into `@types/vscode` and `vscode-test`. See the reasoning here: https://github.com/microsoft/vscode-extension-vscode/issues/147 [Release notes](https://github.com/microsoft/vscode-docs/blob/vnext/release-notes/v1_35.md#splitting-vscode-package-into-typesvscode-and-vscode-test) | [Docs](https://github.com/microsoft/vscode-docs/blob/vnext/api/working-with-extensions/testing-extension.md) Please test: - run `npm install -g generator-code@next` This should install `generator-code@1.2.0-next.0` - `yo code` with TS/JS generates an extension with `@types/vscode` and with integration tests setup using `vscode-test` - You can run the integration test (`yarn test` or running it from debug target) in https://github.com/microsoft/vscode-extension-samples/tree/master/helloworld-test-sample - You can modify the test script and test runner following the [documentation](https://github.com/microsoft/vscode-docs/blob/vnext/api/working-with-extensions/testing-extension.md) - You can easily understand the purpose and usage of https://github.com/microsoft/vscode-dts ( - `vsce` prevents you from publishing an extension when you have `@types/vscode` > `engines.vscode` in package.json.
Test for #71048
Complexity: 2
Overview:
vscodehas been split into@types/vscodeandvscode-test. See the reasoning here: microsoft/vscode-extension-vscode#147Release notes | Docs
Please test:
npm install -g generator-code@nextThis should install
generator-code@1.2.0-next.0yo codewith TS/JS generates an extension with@types/vscodeand with integration tests setup usingvscode-testyarn testor running it from debug target) in https://github.com/microsoft/vscode-extension-samples/tree/master/helloworld-test-samplevsceprevents you from publishing an extension when you have@types/vscode>engines.vscodein package.json.