"TypeScript for Visual Studio" installer not available for 5.1

[wnayes]

Bug Report

There does not appear to be a "TypeScript 5.1 for Visual Studio" installer available on marketplace.visualstudio.com.

Previous releases of TypeScript have had installers made available, such as this one for 5.0.4.

Was it intended to stop publishing this for 5.1 onward?

🔎 Search Terms

Visual Studio 2019/2022, Windows SDK

[fatcerberus]

#54686 seems like it might be related

[HannahOshlag]

5.1.3 has now been published. Here is the link to it: https://marketplace.visualstudio.com/items?itemName=TypeScriptTeam.typescript-513

Apologies that it did not go up immediately. Future publishes should happen simultaneously with the NuGet releases.

[HolgerJeromin]

Does this even work with the buildin node 12 version in VS2019 (or even node 10 in VS2017)?

[cheit-epic]

@noshlag Simultaneous publishes don't seem to be working, since 5.2 is also missing from the marketplace.

[DanielRosenwasser]

Does this even work with the buildin node 12 version in VS2019 (or even node 10 in VS2017)?

Unfortunately no - there are ways of customizing VS2019 to use an alternative version of Node.js, but TypeScript won't work with the built-in Node.js from VS2019.

publishes don't seem to be working, since 5.2 is also missing from the marketplace.

Apologies, there was an oversight in the publishing process. That said, I would highly recommend switching over to using NuGet, or more preferably npm, to customize the version of TypeScript used in VS.

[HolgerJeromin]

Unfortunately no - there are ways of customizing VS2019 to use an alternative version of Node.js, but TypeScript won't work with the built-in Node.js from VS2019.

In my tests this published workaround did not worked at all. This is because
\packages\Microsoft.TypeScript.MSBuild.5.1.3\tools\Microsoft.TypeScript.targets
does not check this registry key at all.
ref #54686 (comment)

IMO this Microsoft.TypeScript.targets from the NuGet package should be adjusted in future releases but I did not find its source. It is easy to check $(registry:HKEY_LOCAL_MACHINE\SOFTWARE\Node.js@InstallPath) in it.

Working workaround is written in a later comment:
#54686 (comment)

[cheit-epic]

Same with 5.5. The beta is there but not the release.
We're working on moving away from relying on the SDK but it's a process.

[HolgerJeromin]

@cheit-epic It was on nuget.org but not anymore (because it was buggy):
#57475 (comment)