Run TypeScript Directly with Node.js 22

It's about to get much easier to run TypeScript directly with Node.js. As of Node.js 22.7.0, there are two experimental command line flags to strip TypeScript types and convert TypeScript-only syntax into JavaScript that can be executed by Node.js.

This even works with import aliases if you make some config and code changes, as demonstrated later. But let's start with the basics first:

How to run TypeScript directly with Node.js:

If your code (or any dependencies) use TypeScript-only features like enum and namespace, you need to use the following command:

If you start many node-processes and want to filter out the ExperimentalWarnings from the log output, you can pass the flag --no-warnings=ExperimentalWarning to get a much cleaner output:

Reading the official guide, I'm especially excited that this brings us a step closer to full TypeScript-support without any external tools or command line flags.

Future versions of Node.js will include support for TypeScript without the need for a command line flag.

How to run TypeScript code with import aliases

One limitation as of Node.js is that import aliases defined via tsconfig.json and the paths option (docs) don't work.

However, there is a workaround available by adding Node.js subpath patterns, defined in the imports field of package.json to achieve the same effect. Let's look at an example:

1. Update configuration

If you have a tsconfig.json defining an @app import alias like this:

Then you can add the following import alias in package.json to make it work almost the same way (more on that in a moment):

NOTE: Import aliases within your own module/code base need to start with the # character. If you know a way to make this work with a custom character like @ or $, please let me know!

2. Update code import statements

To make your code run again, you need to update the imports in your code with a global find all @app and replace with #app.

For example, all your imports like this:

Need to be updated into:

Also note that Node.js requires explicit file extensions when using import aliases. Perhaps it's possible to use without .ts extensions, but at the same time, I think it's good to be explicit - especially since most of the imports are added automatically by the code editor.

Run TypeScript in production

Since this is an experimental feature, it's currently recommended to transpile TypeScript using tsc when building for production. To easily run TypeScript without a separate transpilation step, tsx is still a great choice - learn more here.

However, for development and quick scripts, this is a big boost to productivity!