Encapsulate the TypeScript parser into a separate lib

Create a new project named TypeScript.SyntaxTreeParser and manually convert the TypeScript parser.ts bits into a C# TypeScript parser (from the compiler itself).

• parser.ts
• types.ts

This library will be capable of representing TypeScript type declarations as an abstract syntax tree.

[IEvangelist]

I am curious how you managed to create those hundreds of classes. Were they generated somehow or were they hand-written?

Which classes specifically are you referring to? If you’re talking about the AST branch, then yes, those are hand-written.

Also is the intended work limited to porting parser.ts only or will it one day extend to other APIs like binder.ts, which is responsible for symbol resolution?

The intended work is to make a TypeScript type declaration parser capable of parsing raw .d.ts files and using this metadata to drive my C# source generator. I would define success as being able to source generate arbitrary files, outside the lib.dom.d.ts (which by the way no longer exists), and using that to generate types. As of right now, my project is already capable of source-generating services (interface and class C#), POCOs, and dependency hierarchies.

[trungnt2910]

My project manages to use JSImport because its JS interop architecture is fundamentally different, but that’s out of scope for this issue.

I am curious how you managed to create those hundreds of classes. Were they generated somehow or were they hand-written?

Also is the intended work limited to porting parser.ts only or will it one day extend to other APIs like binder.ts, which is responsible for symbol resolution?

Finally, please tell me if you know some documentation/guides on consuming the TypeScript compiler API from an outside program. I can find things like this but they mostly document the compiler internals and not how to consume those APIs like how one can use Roslyn.