Microsoft.TypeScript.Compiler

Search Terms

Microsoft.TypeScript.Compiler Microsoft.TypeScript.MSBuild nuget tsc.exe standalone

Suggestion

Can you point me towards whatever used to be responsible for making this wrapped exe? I was hoping to use this NuGet package for integration of TypeScript into a project which doesn’t use Node,. The idea of having a self-contained NuGet package to let builds be reproduced in the future without Node installed as appealing to me, but I’m not super in tune with the JavaScript ecosystem in general so I wouldn’t know where to begin on making my own self-contained exe like that. Plan B is to just throw Node and tsc.js into an internal NuGet package, but a self-maintained tsc.exe route seems more elegant if it isn’t a huge ordeal. –@PathogenDavid

This is a reopening of this issue #29689, which had outstanding questions.

In particular, as there environments out here that became dependant on the tsc.exe tooling which was optimal for us in producing TS code, how do we properly recreate the tool if it’s not directly provided anymore?

Or perhaps more pointedly, the tsc build team had the ability to produce this before, would it be possible for them to keep the builds running? There would be a great deal of appreciation if that were the case.

Use Cases

There are many projects out there are shipping or aim to ship some typescript without accepting node as a dependency. Many build chains are heavy and fragile already without adding “the tool to build the tool”. Even if we were to use package manager in our devops efforts, that would just get the tool (node) to build the tool (npm) to get and build the tool (tsc) to build our code…

(this shenanigans has actually prevented us from using some TS projects\libraries (that didn’t have browser builds) as to not add another layer to the statement above)

😐

Examples

Should be:

C:\Users\Dev>tsc -v
Version 3.9.3

Is:

C:\Users\Dev>tsc -v
Version 3.1.5

Checklist

My suggestion meets these guidelines:

• This wouldn’t be a breaking change in existing TypeScript/JavaScript code
• This wouldn’t change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn’t a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
• This feature would agree with the rest of TypeScript’s Design Goals. [10 sounds nice]

[Gerrit0]

I haven’t used this, but it sounds like you want pkg.

https://www.npmjs.com/package/pkg

[DanielRosenwasser]

Nice! Unfortunately I don’t think we can commit to that at this time because we won’t necessarily be trying it ourselves; we already have some trouble tracking down issues due to divergences in runtimes between Node and Electron. Maintaining your own GitHub mirror and implementing a webhook might be a lightweight way to get it yourself though.