How to fix Could not find a declaration file for module 'X' in TypeScript

What this error means

The "Could not find a declaration file for module" error (TS7016) occurs when TypeScript cannot find type definitions for a module you're importing. This is common when using JavaScript libraries that don't include built-in TypeScript support. TypeScript requires declaration files (.d.ts files) to provide type information about JavaScript modules. These files describe the shape of the module's exports without containing actual implementation code. When TypeScript can't find these declarations, it cannot provide type checking or IntelliSense support. The error message typically includes a suggestion like "Try `npm i --save-dev @types/module-name`" which points to the most common solution. Common scenarios include: 1. **Pure JavaScript packages**: Libraries written in JavaScript without TypeScript types 2. **Missing @types packages**: The library has community-maintained types on DefinitelyTyped but they're not installed 3. **Private/internal packages**: Custom modules that need manual type declarations 4. **Legacy packages**: Older libraries that predate TypeScript's popularity

Typical symptoms

• Error TS7016 appears during compilation
• IDE shows 'Could not find a declaration file' warning on import statements
• Error message suggests installing @types package for the module
• IntelliSense and autocomplete don't work for the imported module
• Imported values are implicitly typed as 'any'
• Code runs successfully but TypeScript compilation fails
• Error appears after installing a new JavaScript library

Common causes

1. JavaScript library without built-in TypeScript type definitions
2. Missing @types package from DefinitelyTyped repository
3. Library not listed in DefinitelyTyped (no community types available)
4. Incorrect typeRoots or types configuration in tsconfig.json
5. @types package installed but not in correct node_modules location
6. Using skipLibCheck: false with libraries that have incomplete types
7. Custom or private packages without declaration files
8. Module resolution strategy preventing TypeScript from finding types

How to fix "Could not find a declaration file for module 'X'"

# General pattern
npm install --save-dev @types/package-name

# Common examples:
npm install --save-dev @types/lodash
npm install --save-dev @types/express
npm install --save-dev @types/node
npm install --save-dev @types/react
npm install --save-dev @types/jquery

// This will now have full type support
import _ from "lodash";
import express from "express";

// types/my-library.d.ts
declare module "my-library" {
  // Export the functions/values you're using
  export function someFunction(arg: string): number;
  export const someValue: string;

  // For default exports
  export default function myLibrary(): void;
}

// types/my-library.d.ts
// Quick workaround - types everything as 'any'
declare module "my-library";

{
  "compilerOptions": {
    "typeRoots": ["./node_modules/@types", "./types"]
  },
  "include": ["src/**/*", "types/**/*"]
}

// types/my-library.d.ts
declare module "my-library" {
  export interface Config {
    timeout: number;
    retries: number;
  }

  export class Client {
    constructor(config: Config);
    connect(): Promise<void>;
    disconnect(): void;
  }
}

{
  "compilerOptions": {
    // Explicitly specify where to find type definitions
    "typeRoots": [
      "./node_modules/@types",
      "./types"
    ],

    // Alternative: specify exact packages to include
    "types": ["node", "react", "lodash"],

    // Ensure proper module resolution
    "moduleResolution": "node",
    "esModuleInterop": true
  },
  "include": [
    "src/**/*",
    "types/**/*"
  ]
}

{
  "compilerOptions": {
    "moduleResolution": "node",
    "esModuleInterop": true
  }
}

{
  "compilerOptions": {
    "skipLibCheck": true
  }
}

# Check installed versions
npm list lodash
npm list @types/lodash

# If versions don't match, install compatible @types
npm install --save-dev @types/lodash@4.14.x

# Check package info before installing
npm info @types/package-name versions

// package.json
{
  "dependencies": {
    "express": "^5.0.0"
  },
  "devDependencies": {
    // WRONG - types for Express 4
    "@types/express": "^4.17.0"

    // CORRECT - match major version
    "@types/express": "^5.0.0"
  }
}

// types/package-name.d.ts
// Import from closest version and extend
import type { SomeType } from "@types/package-name-v4";

declare module "package-name" {
  export * from "@types/package-name-v4";
  // Add missing types for v5 features
  export function newV5Feature(): void;
}

# Delete TypeScript build cache
rm -rf node_modules/.cache
rm -rf .tsbuildinfo

# Delete all build output
rm -rf dist build

# Reinstall dependencies
rm -rf node_modules
npm install

# Restart TypeScript server in VS Code
# Cmd/Ctrl + Shift + P → "TypeScript: Restart TS Server"

1. Open command palette (Cmd/Ctrl + Shift + P)
2. Type "TypeScript: Restart TS Server"
3. Press Enter

File → Invalidate Caches → Invalidate and Restart

:CocRestart

Advanced notes

// types/ambient.d.ts
declare module "some-js-library" {
  export function doSomething(): void;
}

// types/assets.d.ts
declare module "*.png" {
  const content: string;
  export default content;
}

declare module "*.css" {
  const classes: { readonly [key: string]: string };
  export default classes;
}

declare module "*.svg" {
  import React from "react";
  export const ReactComponent: React.FC<React.SVGProps<SVGSVGElement>>;
  const src: string;
  export default src;
}

// types/express-extensions.d.ts
import "express";

declare module "express" {
  // Add custom properties to Request
  interface Request {
    user?: {
      id: string;
      email: string;
    };
  }
}

app.get("/profile", (req, res) => {
  // TypeScript knows about req.user
  const userId = req.user?.id;
});

/// <reference types="node" />
/// <reference path="./types/custom.d.ts" />

// Now you can use Node.js types
const buffer: Buffer = Buffer.from("hello");

npx tsc --traceResolution | grep "lodash"

======== Resolving module 'lodash' from '/src/index.ts'. ========
Module resolution kind is not specified, using 'NodeJs'.
Loading module 'lodash' from 'node_modules' folder, target file type 'TypeScript'.
File '/node_modules/@types/lodash/index.d.ts' exist - use it as a name resolution result.
======== Module name 'lodash' was successfully resolved to '/node_modules/@types/lodash/index.d.ts'. ========

// package.json
{
  "name": "my-library",
  "main": "./dist/index.js",
  "types": "./dist/index.d.ts",
  "files": [
    "dist"
  ]
}

// tsconfig.json
{
  "compilerOptions": {
    "declaration": true,
    "declarationMap": true,
    "outDir": "./dist"
  }
}

// WRONG - default import for CommonJS module
import express from "express";
// Error: Module has no default export

// CORRECT
import express = require("express");
// OR with esModuleInterop: true
import express from "express";

// WRONG - declaring with wrong name
declare module "my-lib" {
  // ...
}

// But importing as:
import stuff from "my-lib/v2";  // Won't match!

// CORRECT - match exact import path
declare module "my-lib/v2" {
  // ...
}

// tsconfig.json must include your .d.ts files
{
  "include": [
    "src/**/*",
    "types/**/*"  // Don't forget this!
  ]
}

Frequently asked questions

What does "TS7016" mean?

The "Could not find a declaration file for module" error (TS7016) occurs when TypeScript cannot find type definitions for a module you're importing. This is common when using JavaScript libraries that don't include built-in TypeScript support. ts files) to provide type information about JavaScript modules.

How do I fix "TS7016"?

This TypeScript error appears when importing a JavaScript library that lacks type definitions. TypeScript needs declaration files (.d.ts) to understand the types a module exports. The fix typically involves installing the corresponding @types package or creating custom type declarations.

What causes "TS7016"?

JavaScript library without built-in TypeScript type definitions Missing @types package from DefinitelyTyped repository Library not listed in DefinitelyTyped (no community types available)

Is the "TS7016" error serious?

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

Related errors

• Could not find a declaration file for module 'lodash'

  Could not find a declaration file for module 'lodash'

  MEDIUM

• Constructor of class 'X' is not compatible with constructor signature of type 'Y'

  How to fix 'Constructor of class is not compatible with constructor signature of type' in TypeScript

  HIGH

• Option 'declaration' cannot be used without 'emitDeclarationOnly' when 'noEmit' is set

  How to fix 'declaration cannot be used without emitDeclarationOnly when noEmit is set' in TypeScript

  HIGH

• Type 'T extends U ? X : Y' is not assignable to type 'Z'

  How to fix 'Conditional type is not assignable to' in TypeScript

  MEDIUM

• 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
• 📖
  TypeScript Handbook - Declaration Files Introduction(Official Docs)
• 📖
  TypeScript - Module .d.ts Template(Official Docs)
• 📖
  TypeScript Type Search - DefinitelyTyped(Official Docs)
• DefinitelyTyped - Community Type Definitions Repository
• BobbyHadz - Could not find declaration file for module
• Total TypeScript - Fixing Could Not Find a Declaration File
• Iskander Samatov - Ambient Modules in TypeScript
• Atomist - Fixing the TS7016 Error