How to fix Cannot find module '@types/node' in TypeScript

What this error means

The '@types/node' package contains TypeScript type definitions for Node.js built-in APIs and globals. When you use Node.js-specific features like process.env, __dirname, Buffer, or require() in TypeScript code, the compiler needs these type definitions to understand what these globals are and provide type checking. Without @types/node installed, TypeScript treats these as unknown identifiers and throws module resolution errors. This package is part of the DefinitelyTyped ecosystem, a community-maintained repository of type definitions for JavaScript libraries that don't ship with their own types. By default, TypeScript automatically includes all packages found in node_modules/@types/ during compilation, making type definitions available globally without explicit imports. The error commonly appears when starting a new TypeScript project, after a fresh clone without running npm install, or when the types configuration in tsconfig.json explicitly excludes @types/node from the compilation.

Typical symptoms

• TypeScript compiler errors when using process, Buffer, or __dirname
• Red underlines in IDE on Node.js built-in module imports
• Error message 'Cannot find name process' or similar for Node globals
• Build fails with module resolution errors despite Node.js code working at runtime
• tsconfig.json shows no errors but compilation fails
• Works in JavaScript but breaks when converting to TypeScript

Common causes

1. @types/node package not installed in node_modules (most common)
2. node_modules directory missing or corrupted after git clone
3. Package listed in package.json but npm install never ran
4. tsconfig.json types array explicitly set without including 'node'
5. typeRoots configured incorrectly, excluding node_modules/@types
6. Using pnpm or yarn without proper hoisting configuration
7. skipLibCheck enabled hiding the underlying missing types issue
8. Outdated @types/node version incompatible with TypeScript version

How to fix "Cannot find module '@types/node'"

npm install --save-dev @types/node

# Using Yarn
yarn add -D @types/node

# Using pnpm
pnpm add -D @types/node

{
  "devDependencies": {
    "@types/node": "^20.10.0"
  }
}

rm -rf node_modules package-lock.json
npm install

# pnpm
rm -rf node_modules pnpm-lock.yaml
pnpm install

# Yarn
rm -rf node_modules yarn.lock
yarn install

{
  "compilerOptions": {
    "types": ["node", "jest"] // Include node here
  }
}

{
  "compilerOptions": {
    // Remove the "types" array to auto-include all @types packages
    "moduleResolution": "node"
  }
}

{
  "compilerOptions": {
    "typeRoots": [
      "./node_modules/@types",
      "./types" // Custom types folder (optional)
    ]
  }
}

# Check your Node.js version
node --version  # e.g., v20.10.0

# Install matching types
npm install --save-dev @types/node@20

# Node.js 20.x
npm install -D @types/node@20

# Node.js 18.x
npm install -D @types/node@18

# Node.js 16.x
npm install -D @types/node@16

Advanced notes

Frequently asked questions

What does "TS2307" mean?

js built-in APIs and globals. env, __dirname, Buffer, or require() in TypeScript code, the compiler needs these type definitions to understand what these globals are and provide type checking. Without @types/node installed, TypeScript treats these as unknown identifiers and throws module resolution errors.

How do I fix "TS2307"?

This error occurs when TypeScript cannot locate the Node.js type definitions package. It typically happens when using Node.js built-in modules (like process, Buffer, or require) in TypeScript without having @types/node installed as a development dependency.

What causes "TS2307"?

@types/node package not installed in node_modules (most common) node_modules directory missing or corrupted after git clone Package listed in package.json but npm install never ran

Is the "TS2307" error serious?

It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Related errors

• Cannot find name 'X'

  How to fix 'Cannot find name X' error in TypeScript

  HIGH

• Cannot find module './X'

  How to fix "Cannot find module './X'" in TypeScript

  MEDIUM

• Cannot find name 'Buffer'

  Cannot find name 'Buffer'

  MEDIUM

• Cannot find module 'react'

  Cannot find module 'react'

  HIGH

• Cannot find name 'process'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node` and then add 'node' to the types field in your tsconfig.

  How to fix "Cannot find name 'process'" in TypeScript

  MEDIUM

• Module has no exported member 'X'

  How to fix 'Module has no exported member X' error in TypeScript

  MEDIUM

Official resources & further reading

• 📚TypeScript Official Documentation
• 📖
  @types/node npm Package(Official Docs)
• 🐙
  DefinitelyTyped Repository(GitHub)
• 📖
  TypeScript Declaration Files Publishing(Official Docs)