Retire typespec-vs and typespec-vscode npm packages

[timotheeguerin]

Those packages don't have a reason to exist today, we publish to the marketplace they only existed as previous tools.

That also means retire the tsp code install/uninstall and tsp vs install/uninstall commands or find a way to have those connect to the marketplace instead(ideal)

[github-actions]

🎯 Issue Triage

Request to retire the typespec-vs and typespec-vscode npm packages, which are now obsolete since the extensions are published directly to the marketplace. Also covers retiring or updating the tsp code install/uninstall and tsp vs install/uninstall CLI commands.

Category: Feature Request
Area: ide

🔍 Analysis

• The typespec-vs and typespec-vscode npm packages were originally used as distribution vehicles for the VS and VS Code extensions, but extension marketplace publishing has since made them redundant.
• The CLI commands tsp code install/uninstall and tsp vs install/uninstall currently depend on these packages; they should either be removed or redirected to trigger marketplace installs.
• Retiring the packages will reduce maintenance burden and avoid confusion for users who might try to install extensions via npm.
• The ideal path for the CLI commands is to redirect to the VS/VS Code marketplace (e.g., via code --install-extension or opening the marketplace URL), preserving a good user experience while removing the obsolete packages.

📝 Suggested next steps

• Deprecate (or remove) the typespec-vscode and typespec-vs npm packages
• Update or remove tsp code install/uninstall — consider delegating to code --install-extension ms-typespec.typespec-vscode
• Update or remove tsp vs install/uninstall — consider pointing to the Visual Studio Marketplace
• Add deprecation notices in the packages' READMEs and/or package.json before removal

Generated by Agentic Triage