Skip to content


Replace node with tsx

tsx is a drop-in replacement for node, meaning you can use it the exact same way (supports all command-line flags).

If you have an existing node command, simply substitute tsx.

node --no-warnings --env-file=.env ./file.js

tsx --no-warnings --env-file=.env ./file.js

Node.js version matters

Under the hood, tsx calls node. This means the supported features in tsx depends on the version of Node.js you have installed.


No type-checking

tsx allows you to execute TypeScript code directly without performing type checks.

Modern code editors, such as VSCode and WebStorm, use IntelliSense to provide real-time type checking. This feature offers immediate feedback on type errors and coding guidance, diminishing the need for frequent manual type checks previously performed using tsc.

By treating type checking as a linting step rather than a compilation requirement, and deferring it to commit hooks or CI checks, devs can view type errors as non-blocking warnings. This approach promotes more flexible and rapid iteration. After all, types are safeguards to ensure correct function usage and may often be imperfect during the iterative phases of development.

If you'd really like to type check before running the code, you still can:

tsc --noEmit && tsx ./file.ts

Custom tsconfig.json path

By default, tsconfig.json is detected from the current working directory.

To set a custom path, use the --tsconfig flag:

tsx --tsconfig ./path/to/tsconfig.custom.json ./file.ts

Alternatively, use the TSX_TSCONFIG_PATH environment variable:

TSX_TSCONFIG_PATH=./path/to/tsconfig.custom.json tsx ./file.ts


Start a TypeScript REPL by running tsx with no arguments: