Solve - ts-node: command not found error

avatar

Borislav Hadzhiev

Last updated: Mar 10, 2022

banner

Photo from Unsplash

'Solve - ts-node: command not found error' #

Use npx to solve the error "ts-node: command not found", e.g. npx ts-node or install the package globally by running npm install -g ts-node to be able to use the command without the npx prefix.

command not found ts node

The fastest way to solve the error is to use the npx command.

shell
npx ts-node myScript.ts npx ts-node --version

Alternatively, you can install ts-node globally or as a development dependency.

shell
# 👇️ installs ts-node globally (can run from any directory) npm install -g ts-node npm install -g typescript # 👇️ installs ts-node locally to the project (must be ran from root directory) npm install --save-dev ts-node typescript
The benefit of installing ts-node locally to your project is - it enables you to control and share the versions through your package.json file.

If you decide to install the package locally, you would add a script to your package.json file and not interface with the ts-node command directly.

If the global installation of ts-node fails, you might have to run the command prefixed with sudo.

shell
# 👇️ if you get permissions error sudo npm install -g ts-node sudo npm install -g typescript ts-node myScript.ts ts-node --version

You can link your project to the globally installed ts-node package, by opening your terminal in your project's root directory (where your package.json file is) and running the npm link ts-node command.

shell
npm link ts-node

The npm link command creates a symbolic link from the globally installed package to the node_modules/ directory of the current folder.

If the "ts-node: command not found" error is not resolved, try restarting your terminal.

If that doesn't help, run the following command:

shell
npm config get prefix

The command will show you the path where npm puts your globally installed packages. The global packages will be in the bin directory at the specified path.

Look at the PATH environment variable on your operating system and add the path that the npm config get prefix command outputs, if it's not already there.

If you add the output from the command to your PATH environment variable, you have to restart any open command prompts before it takes effect.

If that didn't work, try to add the path to the bin folder (from npm config get prefix) to your PATH environment variable and restart your terminal.

For example, on macOS, you can update your path with the following command:

shell
# make sure path matches with npm config get prefix export PATH=/usr/local/share/npm/bin:$PATH

And on Windows, the output of the npm config get prefix command will look something like: C:\Users\Your_User_Name\AppData\Roaming\npm.

Edit the environment variable on your machine and add the specified path (replacing the placeholder with your username).

If you are on linux, you can add the output from the npm config get prefix command to your .bashrc file.

~/.bashrc
# 👇️ make sure to update the path with the output # from the command export PATH="/usr/local/share/npm/bin:$PATH"
If you add the output from the command to your PATH environment variable, you have to restart any open command prompts before it takes effect.

If that doesn't help try to reinstall Node.js on your machine and then install ts-node globally by running npm install -g typescript ts-node.

During the installation you might get a prompt for whether you want to automatically update the PATH environment variable on your system, make sure to tick the option.
shell
# 👇️ installs ts-node globally (can run from any directory) npm install -g ts-node npm install -g typescript # 👇️ installs ts-node locally to the project (must be ran from root directory) npm install --save-dev ts-node typescript

If the global installation of ts-node fails, you might have to run the command prefixed with sudo.

shell
# 👇️ if you get permissions error sudo npm install -g ts-node sudo npm install -g typescript ts-node myScript.ts ts-node --version

Alternatively, you can see how you can fix the permissions error on this page in the official npm docs.

I wrote a book in which I share everything I know about how to become a better, more efficient programmer.
book cover
You can use the search field on my Home Page to filter through all of my articles.