How to fix Cannot find TypeScript compiler for ts-node in TypeScript

TypeScriptINTERMEDIATEMEDIUMUpdated Dec 11, 2025· 143 views

This error occurs when ts-node cannot locate the TypeScript compiler (typescript package) needed to transpile TypeScript code. It typically happens when TypeScript is not installed globally or locally, or when ts-node cannot resolve the TypeScript package path. The fix involves ensuring TypeScript is properly installed and accessible to ts-node.

Quick fix

Fixes Cannot find TypeScript compiler for ts-node

# Using npm
npm install --save-dev typescript

# Using yarn
yarn add --dev typescript

# Using pnpm
pnpm add --save-dev typescript
  1. Install TypeScript in your project
  2. Check global TypeScript installation
  3. Verify ts-node can find TypeScript
  4. Clear npm cache and reinstall dependencies
typescript — error
# Using npm
npm install --save-dev typescript
# Using yarn
yarn add --dev typescript
# Using pnpm
pnpm add --save-dev typescript
Cannot find TypeScript compiler for ts-node

What this error means

The "Cannot find TypeScript compiler for ts-node" error is thrown by the ts-node runtime when it attempts to compile TypeScript code but cannot locate the TypeScript compiler package (typescript). This happens because: 1. **ts-node Dependency**: ts-node is a TypeScript execution engine that runs TypeScript code directly in Node.js without pre-compilation. It requires the TypeScript compiler (typescript package) to be available. 2. **Compiler Resolution**: When you run ts-node, it searches for the TypeScript compiler in several locations: - Local node_modules (project directory) - Global npm/yarn installation - Paths specified in tsconfig.json or ts-node configuration 3. **Common Scenarios**: - TypeScript is not installed in the project (missing from package.json) - Global TypeScript installation is not accessible - ts-node is running in a different environment than expected - Package manager issues (npm/yarn/pnpm) preventing proper resolution 4. **Impact**: Without the TypeScript compiler, ts-node cannot transpile TypeScript code to JavaScript, preventing execution of TypeScript files directly with Node.js.

Typical symptoms

  • Error message: "Cannot find TypeScript compiler for ts-node" when running TypeScript files
  • ts-node commands fail immediately with compiler not found error
  • Works in some environments but fails in others (CI/CD, production)
  • Error occurs after fresh project setup or dependency installation
  • Running "npx ts-node index.ts" fails with compiler error
  • TypeScript files cannot be executed directly with ts-node

Common causes

  1. TypeScript package not installed in project dependencies
  2. Global TypeScript installation missing or not in PATH
  3. ts-node running from different directory than project root
  4. Package manager lockfile issues (package-lock.json, yarn.lock)
  5. Node.js module resolution paths misconfigured
  6. ts-node version incompatible with installed TypeScript version
  7. Project uses workspaces/monorepo structure causing resolution issues

How to fix "Cannot find TypeScript compiler for ts-node"

1Install TypeScript in your project

First, ensure TypeScript is installed in your project. Run this command in your project directory:

bash
# Using npm
npm install --save-dev typescript

# Using yarn
yarn add --dev typescript

# Using pnpm
pnpm add --save-dev typescript

Verify installation by checking package.json:

json
{
  "devDependencies": {
    "typescript": "^5.0.0"
  }
}

Also check that node_modules/typescript exists:

bash
ls node_modules/typescript
2Check global TypeScript installation

If using global TypeScript, verify it's installed and accessible:

bash
# Check global TypeScript installation
npm list -g typescript

# Or check if tsc is available
tsc --version

# If not installed globally:
npm install -g typescript

Note: Global installations can cause version conflicts. Prefer local project installation for consistency.

3Verify ts-node can find TypeScript

Test if ts-node can locate TypeScript by running:

bash
# Check ts-node version
npx ts-node --version

# Try a simple test
npx ts-node -e "console.log('Hello from ts-node')"

If this fails, check the module resolution path:

bash
# Debug module resolution
node -e "console.log(require.resolve('typescript'))"

# Check if ts-node can find typescript
node -e "console.log(require('ts-node').register().compiler)"
4Clear npm cache and reinstall dependencies

Package manager cache issues can cause resolution problems:

bash
# Clear npm cache and reinstall
npm cache clean --force
rm -rf node_modules package-lock.json
npm install

# For yarn
yarn cache clean
rm -rf node_modules yarn.lock
yarn install

# For pnpm
pnpm store prune
rm -rf node_modules pnpm-lock.yaml
pnpm install

After reinstalling, test ts-node again:

bash
npx ts-node index.ts
5Configure ts-node with explicit TypeScript path

If automatic resolution fails, specify TypeScript path explicitly:

Create or update tsconfig.json:

json
{
  "ts-node": {
    "compiler": "typescript",
    "compilerOptions": {
      "module": "commonjs"
    }
  },
  "compilerOptions": {
    "target": "es2020",
    "module": "commonjs"
  }
}

Or use command-line options:

bash
# Specify compiler explicitly
npx ts-node --compiler typescript index.ts

# Or with require flag
npx ts-node --compiler-options '{"module":"commonjs"}' index.ts
6Check for version compatibility issues

Ensure ts-node and TypeScript versions are compatible:

bash
# Check versions
npx ts-node --version
npx tsc --version

# Update to compatible versions if needed
npm install --save-dev ts-node@latest typescript@latest

# Or specify compatible versions in package.json

Common compatibility matrix:
- ts-node v10+ requires TypeScript v4.0+
- Older ts-node versions may need older TypeScript

Check the ts-node documentation for version compatibility.

Advanced notes

### Understanding ts-node Architecture

ts-node works by:
1. Registering a require() hook that intercepts .ts file imports
2. Using the TypeScript compiler API to transpile code on-the-fly
3. Caching compiled results for performance

### Module Resolution Details

Node.js resolves modules in this order:
1. Core modules (fs, path, etc.)
2. node_modules in current directory
3. node_modules in parent directories (up to root)
4. Global NODE_PATH (if set)
5. Global npm installation

ts-node adds TypeScript-specific resolution:
- Checks tsconfig.json "compilerOptions.paths"
- Respects "baseUrl" and "paths" mappings
- Can use custom module resolution via "ts-node/register"

### Common Pitfalls

1. Monorepo Workspaces: In monorepos, ts-node might look for TypeScript in the wrong workspace. Use:

bash
# From package directory
   cd packages/my-package
   npx ts-node index.ts

2. Docker/Container Environments: Ensure node_modules is properly mounted and TypeScript is installed in the container.

3. CI/CD Pipelines: Cache node_modules but ensure TypeScript is included in devDependencies.

4. Symlinked Packages: npm/yarn link can cause resolution issues. Use:

bash
npm install --no-bin-links

### Alternative Solutions

If ts-node continues to fail:
1. Use tsc + node: Compile first, then run:

bash
npx tsc index.ts
   node index.js

2. Use tsx: Alternative TypeScript runtime:

bash
npm install --save-dev tsx
   npx tsx index.ts

3. Use SWC: Faster compilation with @swc-node:

bash
npm install --save-dev @swc-node/register
   node -r @swc-node/register index.ts

### Debugging Tips

Enable verbose logging:

bash
DEBUG=ts-node npx ts-node index.ts

Check require cache:

bash
node -e "console.log(Object.keys(require.cache).filter(k => k.includes('typescript')))"

Test with minimal example:

typescript
// test.ts
console.log('Test');
bash
npx ts-node test.ts

Frequently asked questions

What does "Cannot find TypeScript compiler for ts-node" mean?
The "Cannot find TypeScript compiler for ts-node" error is thrown by the ts-node runtime when it attempts to compile TypeScript code but cannot locate the TypeScript compiler package (typescript). This happens because: 1. js without pre-compilation.
How do I fix "Cannot find TypeScript compiler for ts-node"?
This error occurs when ts-node cannot locate the TypeScript compiler (typescript package) needed to transpile TypeScript code. It typically happens when TypeScript is not installed globally or locally, or when ts-node cannot resolve the TypeScript package path. The fix involves ensuring TypeScript is properly installed and accessible to ts-node.
What causes "Cannot find TypeScript compiler for ts-node"?
TypeScript package not installed in project dependencies Global TypeScript installation missing or not in PATH ts-node running from different directory than project root
Is the "Cannot find TypeScript compiler for ts-node" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading