ts-node VS TypeScript-Call-Graph

use ts-node

tsx : for typescript code execution. It is a replacement of ts-node. As the latter does not work in Node 20

I thought this was going to be a project like ts-node [1]

[1] https://github.com/TypeStrong/ts-node

The command specified in the app option uses ts-node by default, which is an execution engine for Node.js that allows you to run TypeScript code directly. The --prefer-ts-exts flag prevents ts-node from prioritizing precompiled .js files and will always import the TypeScript source code instead, if it is available. This is useful if you are also using tsc (the TypeScript compiler) alongside the app option. The bin/cdk.ts file is the entry point for our CDK app, which defines the main function that will be executed when the app is run.

If you want to write apps that run on Node.js I would suggest using Google’s TypeScript style guide. You can start using it by simply running npx gts init. I’d suggest that you start with this and run your apps using ts-node/ts-node-dev because it does not require an extra build step.

ts-node (“TypeScript execution and REPL for Node.js”)

Here is a relevant discussion and dev comment: https://github.com/TypeStrong/ts-node/issues/155

Specifically for TypeScript I created a CLI to visualize the call graph

https://github.com/whyboris/TypeScript-Call-Graph

Works for _functions_ not classes. I'm unsure how useful this tool is, but I suspect it might be helpful in some codebases.

A slightly-related project I created: TypeScript Call Graph - generate/visualize a call graph of your TypeScript files in a variety of ways. MIT open source ;)

https://github.com/whyboris/TypeScript-Call-Graph

Mildly-related project I have: generate call graph for typescript files

https://github.com/whyboris/TypeScript-Call-Graph

The TypeScript language service is really neat -- you can use it to parse through .ts files so you can, for example, see which functions call which functions.