-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Engineering work for vscode-test and @types/vscode #71048
Comments
Update vscode-test & @types/vscode usage for microsoft/vscode#71048
Thanks a lot @octref for the related work on supporting the vscode types and test runner in a more npm-first-class manner! This seemed like a wart last time I refreshed the rls-vscode extension (Rust support), so I'd consider the work very needed. Is there a timeline on when it is recommended to switch over to |
See microsoft/vscode#71048 for more details.
@Xanewok You can wait until next Wednesday for new release, or read the to-be-released docs here:
Yes, you can switch already. |
See microsoft/vscode#71048 for more details.
In continuation of #70175. There a few things I'd want to sort out before we can recommend people switching to vscode-test and
@types/vscode
Already done:
@types/vscode
: 1.14 - 1.32For
@types/vscode
@types/vscode
when pushing tag to vscode release branch.vscode-dts
, so we can runnpx vscode-dts dev
ornpx vscode-dts 1.30
etc for testing: https://github.com/microsoft/vscode-dtsFor vscode-test:
Remove lib/shared and update install script Remove lib/shared and update install script vscode-extension-vscode#154vscode-test
Move test runner tovscode-test
vscode-extension-vscode#157The text was updated successfully, but these errors were encountered: