Fix “tsc: command not found” When Installing TypeScript on macOS

You will learn how the TypeScript compiler is installed through npm, why a successful global installation may still produce tsc: command not found, and how the shell PATH determines whether a command can run. You will also learn commands for checking npm’s installation locations and reliable alternatives such as npx and project-local TypeScript installations.

The tsc command is the TypeScript compiler command-line interface (CLI). It is included in the typescript npm package.

When you run:

npm install -g typescript

npm installs TypeScript into its global package directory. It also creates a runnable command named tsc in npm’s global bin directory.

Your terminal does not search every folder on your computer when you type a command. Instead, it searches only the directories listed in the PATH environment variable. Therefore, this error:

tsc: command not found

usually means one of these things:

• TypeScript was not installed successfully.
• npm created tsc, but npm’s global bin directory is missing from PATH.
• You installed TypeScript under a different Node/npm installation than the one your shell currently uses.
• The terminal session needs to be restarted after changing configuration.

This distinction matters because installing a package and making its executable discoverable are related, but separate, steps.

Think of npm’s global bin directory as a tool drawer and PATH as a list of drawers your terminal is allowed to open.

Installing TypeScript puts the tsc tool into npm’s drawer. When you type tsc, your shell checks each drawer listed in PATH.

• If npm’s drawer is on the list, the shell finds and runs tsc.
• If it is not on the list, the shell reports command not found even though the tool may already be installed.

The fix is not necessarily reinstalling TypeScript. Often, the fix is telling the shell where npm keeps globally installed commands.

The TypeScript compiler is installed with npm:

npm install -g typescript

Verify that npm considers TypeScript globally installed:

npm list -g --depth=0 typescript

A successful result includes a version, similar to:

/usr/local/lib
└── typescript@5.7.2

Find npm’s global executable directory:

npm bin -g

On older npm versions, this commonly prints a directory such as:

/usr/local/bin

Check whether the tsc executable exists there:

ls -l "$(npm bin -g)/tsc"

If it exists, try running it through its full path:

"$(npm bin -g)/tsc" --version

If this prints a TypeScript version, TypeScript is installed correctly. The remaining issue is that the global bin directory is not available through PATH.

To see where the shell currently finds , use:

Consider this diagnostic sequence:

npm install -g typescript
npm list -g --depth=0 typescript
npm bin -g
ls -l "$(npm bin -g)/tsc"
"$(npm bin -g)/tsc" --version

What happens at each step:

1. npm install -g typescript downloads and installs the global typescript package.
2. npm list -g --depth=0 typescript asks npm whether that package exists in the global package list.
3. npm bin -g prints the directory where npm places global executable commands.
4. ls -l "$(npm bin -g)/tsc" checks whether the tsc command file was created in that directory.
5. "$(npm bin -g)/tsc" --version runs that exact file directly, without relying on PATH.

For example, if npm bin -g prints /usr/local/bin, the final command is effectively:

/usr/local/bin/tsc --version

If the direct command works but this does not:

TypeScript compilation is commonly used in several workflows:

• Frontend applications: Compile .ts and .tsx source files into JavaScript before browser deployment.
• Node.js APIs: Type-check server code during development and build JavaScript for production.
• CI pipelines: Run tsc --noEmit to catch type errors before merging a pull request.
• Libraries: Generate JavaScript and declaration files (.d.ts) for package consumers.
• Editor integration: Language tools use the project’s TypeScript version to provide diagnostics and autocomplete.

In all of these cases, the project needs a dependable way to locate the compiler. That is why project-local installation is usually preferred over relying on a developer’s global installation.

In most production codebases, TypeScript is installed locally as a development dependency rather than globally:

npm install --save-dev typescript

The executable is then available in node_modules/.bin. npm automatically exposes that directory to scripts in package.json:

{
  "scripts": {
    "typecheck": "tsc --noEmit",
    "build": "tsc -p tsconfig.json"
  }
}

Run the scripts with:

npm run typecheck
npm run build

This pattern is valuable because every developer and CI server uses the version recorded in package.json and the lockfile.

You can also run a locally installed compiler directly with npx:

npx tsc --version
npx tsc --noEmit

For one-off execution, npx looks for the project-local executable first. This avoids many global problems.

Assuming installation automatically updates PATH

This can fail even after a successful install:

npm install -g typescript
tsc --version

Installing creates the command, but your shell must be able to search its directory. Check it with:

npm bin -g
echo "$PATH"

Adding the global package directory instead of the bin directory

These are different locations:

npm root -g  # Global packages, such as .../lib/node_modules
npm bin -g   # Executable commands, such as .../bin

For tsc, add the result of npm bin -g to PATH, not the result of npm root -g.

Using sudo as the first solution

This is tempting:

sudo npm install -g typescript

It can create files owned by root, causing later permission problems. First inspect your Node and npm setup. Node version managers and project-local dependencies are usually safer approaches.

# Install TypeScript globally
npm install -g typescript

# Verify the global package installation
npm list -g --depth=0 typescript

# Print global package directory
npm root -g

# Print global executable directory
npm bin -g

# Check whether the global tsc file exists
ls -l "$(npm bin -g)/tsc"

# Run global tsc by exact path
"$(npm bin -g)/tsc" --version

# Check whether the shell can find tsc
command -v tsc

# Inspect command search directories
echo "$PATH"

# Add npm global commands to PATH for the current shell session
export PATH="$(npm bin -g):$PATH"

# Recommended for a project
npm install --save-dev typescript
npx tsc --version

Key rule: npm root -g is for package files; npm bin -g is for commands such as tsc.

Why does tsc: command not found happen after installing TypeScript?

Usually, npm installed TypeScript but its global executable directory is not in your shell’s PATH. Verify with npm list -g --depth=0 typescript and npm bin -g.

How do I check whether TypeScript is installed globally?

Run:

npm list -g --depth=0 typescript

If it displays typescript@..., npm has it in the global package list.

Where is the tsc executable installed?

Run:

npm bin -g

The tsc executable should be in that directory. Check it with:

ls -l "$(npm bin -g)/tsc"

What is the difference between npm root -g and npm bin -g?

npm root -g shows where package source files are stored. shows where runnable commands, including , are linked or created.

• Environment variables — PATH is an environment variable that controls where the shell searches for commands.
• Shell configuration files — Files such as ~/.bash_profile and ~/.zshrc configure command-line sessions.
• npm global vs local installation — Explains the difference between machine-wide tools and project dependencies.
• package.json scripts — Provides repeatable, project-specific commands such as npm run build.
• npx — Runs locally installed npm command-line tools conveniently.
• Node.js version managers — Tools such as nvm can change npm’s global installation prefix and help avoid permission issues.
• tsconfig.json — Stores TypeScript compiler settings for a project.
• TypeScript compilation — Covers converting TypeScript into JavaScript and checking types.