Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Node.js, PHP and APIs

TypeScript cannot find the type definition file for 'node'

Errorerror TS2688: Cannot find type definition file for 'node'.

Short answer

TS2688 means tsconfig asks for the 'node' type package, and TypeScript cannot find it where it looks. Install @types/node as a dev dependency in the same project, and check that typeRoots or a parent folder does not hide node_modules/@types. Do not just delete the types line unless you do not use Node.js globals.

  • Applies to TypeScript 5.8, @types/node 22, Angular 19
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Check that the package is present and see which tsconfig settings decide what is loaded.

    ls node_modules/@types/node/package.json
    npx tsc --showConfig | grep -A4 -E '"types"|typeRoots'
  2. 2Match what you see, then jump to its fix

    1. 1ls cannot find node_modules/@types/node@types/node is not installed in this projectFix
    2. 2@types/node exists, yet the error stays; tsconfig has a typeRoots entrytypeRoots points somewhere that does not contain @typesFix

What does the error look like?

  • error TS2688: Cannot find type definition file for 'node'.
  • The file is in the program because: Entry point of type library 'node' specified in compilerOptions
  • Cannot find name 'process'. Do you need to install type definitions for node?

Cause 1 of 2

@types/node is not installed in this project

1Check

The tsconfig names 'node' in the types array, but the package that holds those declarations was never installed.

npm ls @types/node

2Fix

Install it as a dev dependency, matching your Node.js major version.

npm install --save-dev @types/node@22

3Verify

The compiler passes.

npx tsc --noEmit

Confirmed by typescriptlang.org

Did this fix it?

Cause 2 of 2

typeRoots points somewhere that does not contain @types

1Check

Once typeRoots is set, only the folders listed there are searched, and node_modules/@types is no longer included.

grep -n -B1 -A3 typeRoots tsconfig*.json

2Fix

Add node_modules/@types to the list, or remove typeRoots if you did not need it.

{
  "compilerOptions": {
    "typeRoots": ["./node_modules/@types", "./typings"]
  }
}

3Verify

Run the compiler again.

npx tsc --noEmit

Confirmed by typescriptlang.org

Did this fix it?

How do I stop it coming back?

  • Install @types/node in every package of a monorepo that lists 'node' in types.
  • Keep the @types/node major version equal to the Node.js major you run.
  • Remember that from TypeScript 6.0 the default for types is an empty list, so globals need an explicit entry.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Back end

cdk synth says --app is required

--app is required either in command-line, in cdk.json or in ~/.cdk.json

The CDK CLI needs a command that runs your app and finds it in three places: the --app option, cdk.json in the project folder, or cdk.json in your home folder.

3 causes, each with a fix

Back end

Mocha or Node cannot find ts-node/register

Error: Cannot find module 'ts-node/register'

Node resolves ts-node/register from your project's node_modules, so the package must be installed there, next to typescript.

2 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.