tsc reports type errors in files under node_modules
node_modules/@types/some-package/index.d.ts(12,5): error TS2300: Duplicate identifierShort answer
tsc type-checks every declaration file it loads, including the .d.ts files of your dependencies. Set skipLibCheck to true to skip checking them, and set an explicit types list so tsc stops loading every @types package it finds. Your own code is still fully checked.
Fix it fast
1Find out which cause you have
List which files the errors come from. If every path starts with node_modules, this page applies.
npx tsc --noEmit | grep -c node_modules2Match what you see, then jump to its fix
- 1
Errors in node_modules/**/*.d.ts that you did not write and cannot editDeclaration files of dependencies are being type-checkedFix - 2
Errors come from @types packages your project never uses, such as test or tooling typings pulled in by another packageEvery installed @types package is pulled into the buildFix
- 1
What does the error look like?
node_modules/@types/some-package/index.d.ts(12,5): error TS2300: Duplicate identifiererror TS2688: Cannot find type definition file for '...'
Cause 1 of 2
Declaration files of dependencies are being type-checked
1Check
By default tsc also checks declaration files. A package whose typings need a newer TypeScript, or two typings that clash, then fail your build for reasons outside your code.
npx tsc --version && npm ls typescript2Fix
Turn on skipLibCheck. It skips type checking of declaration files, at the cost of some accuracy in the type system.
{
"compilerOptions": {
"skipLibCheck": true
}
}3Verify
Run the type check again; errors from node_modules should be gone.
npx tsc --noEmitConfirmed by typescriptlang.org
Cause 2 of 2
Every installed @types package is pulled into the build
1Check
Before TypeScript 6.0, when types is not set, all visible @types packages are included. That drags in typings you never asked for.
ls node_modules/@types2Fix
List only the typings you need. When types is set, only those packages go into the global scope.
{
"compilerOptions": {
"types": ["node"]
}
}3Verify
Type-check again.
npx tsc --noEmitConfirmed by typescriptlang.org
How do I stop it coming back?
- Set skipLibCheck and types in the first tsconfig of a project.
- Keep one typescript version in the tree; check it with npm ls typescript after upgrades.
- Update @types packages together with the packages they describe.
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:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- WorkforceA field app, an admin console and a self-hosted Node.js server for push and reconciliation.
Related fixes
Back end
TypeScript cannot find '@angular/platform-browser' in an Angular project
Cannot find module '@angular/platform-browser' or its corresponding type declarations.
TS2307 means TypeScript could not turn the import into a file.
3 causes, each with a fixBack end
Angular build fails with TS2707 or "has no exported member" after installing a library
Module '"@angular/core"' has no exported member
These errors mean a library was compiled by a newer Angular than your app uses.
3 causes, each with a fixBack 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 fixBack end
TypeScript cannot find module '@nestjs/core' or its type declarations
error TS2307: Cannot find module '@nestjs/common' or its corresponding type declarations.
TS2307 means TypeScript searched node_modules and found neither the package nor its types.
3 causes, each with a fixBack 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 fixBack end
TypeError: Class constructor cannot be invoked without 'new' in compiled TypeScript
TypeError: Class constructors cannot be invoked without 'new'
Node.js throws this when a native class is called like a plain function.
2 causes, each with a fix