typescript-transformer-handbook VS ts-morph

I recently learned about Typescript transformers[0] and wish they were better supported in a first-class manner. Working with ttypescript or ts-patch[1] is easy enough, but it still feels like you're doing something you shouldn't be doing.

My goal was to pass the Typescript types to the JS runtime, maybe there's a better way and GPT-4 just led me astray...

[0] https://github.com/itsdouges/typescript-transformer-handbook

[1] https://github.com/nonara/ts-patch

I would start by researching TypeScript transforms and ts-morph.

I recently came across an incredibly powerful tool called ts-morph. It's an Abstract Syntax Tree (AST) code analyzer and manipulator that can easily locate class declarations and their references. Just remember, it only works on TypeScript files. To use it, we created a new "build.ts" file and harnessed the full potential of Bun's API. Because ts-morph only understands TypeScript files, we bundled our files accordingly.

I'll definitely look into these two generation suggestions, one I found from a quick google search was [ts-morph](https://github.com/dsherret/ts-morph/tree/latest/packages/ts-morph), but I haven't looked into it further yet.

ts-morph may also help.

The declarations (functions, variables, classes ...) and their docs are extracted with a custom API extractor I built based on the ts-morph library and the TypeScript compiler.

There are a couple of ways. Like you mentioned Babel has various features that count as language extensions and there's also SweetJS. I've been interested in exploring the compiler API personally and ts-morph.