Repository: TypeScript
Issue: Microsoft.TypeScript.Compiler
Labels: Visual Studio

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## Search Terms

<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->
Microsoft.TypeScript.Compiler
Microsoft.TypeScript.MSBuild
nuget
tsc.exe
standalone

## Suggestion

<!-- A summary of what you'd like to see added or changed -->

> 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

<!-- Show how this would be used and what the behavior would be -->
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:

* [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [X] This wouldn't change the runtime behavior of existing JavaScript code
* [X] This could be implemented without emitting different JS based on the types of the expressions
* [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [X] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals). [10 sounds nice]