The fork does not use the VSCode extension. The CI install also failed,
because the extension ran tsx from a prepare script and never
declared tsx as a dependency.
Remove both integrations/vscode packages, the release-vsix workflow,
the workspace glob, and the debug launch config. The host plugin was a
stub with no dependents.
Description
Linked Issues
Additional Context
The fork does not use the VSCode extension. The CI install also failed,
because the extension ran `tsx` from a `prepare` script and never
declared `tsx` as a dependency.
Remove both `integrations/vscode` packages, the release-vsix workflow,
the workspace glob, and the debug launch config. The host plugin was a
stub with no dependents.
## Description
<!-- Please insert your description here and especially provide info about the "what" this PR is solving -->
## Linked Issues
<!-- Optional, if you have any -->
## Additional Context
<!-- e.g. is there anything you'd like reviewers to focus on? -->
The fork does not use the VSCode extension. The CI install also failed,
because the extension ran `tsx` from a `prepare` script and never
declared `tsx` as a dependency.
Remove both `integrations/vscode` packages, the release-vsix workflow,
the workspace glob, and the debug launch config. The host plugin was a
stub with no dependents.
Some required checks failed
autofix.ci / autofix (pull_request) Failing after 18m46s
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The fork does not use the VSCode extension. The CI install also failed,
because the extension ran
tsxfrom apreparescript and neverdeclared
tsxas a dependency.Remove both
integrations/vscodepackages, the release-vsix workflow,the workspace glob, and the debug launch config. The host plugin was a
stub with no dependents.
Description
Linked Issues
Additional Context
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.