SECURITY WARNING: Never run commands you don't understand. Always review code before execution. Use at your own risk.
FixMyError.net
TypeScript New Added 28 August 2026

TypeScript: The inferred type of X cannot be named without a reference to Y

When emitting declaration files, TypeScript needs to write out the type of an exported value, but that type lives in a package that is not a direct dependency, so the generated .d.ts would reference something consumers cannot resolve.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix
// 1. Annotate the export explicitly so inference is not needed
import type { Router } from 'express';
export const router: Router = makeRouter();

// 2. Or promote the transitive package to a direct dependency
npm i -D @types/express

// 3. Or disable declaration emit for that entry point
// tsconfig.json -> "declaration": false

How to diagnose TypeScript errors

TypeScript errors are the compiler describing a mismatch between what you declared and what you did. Nearly all of them fall into assignability (this shape is not that shape), missing declarations (a JavaScript package with no types), or strict null checks (a value can be undefined on a path you did not handle). Casting with as or any silences the message without fixing the underlying mismatch, which usually reappears at runtime.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

  1. Read the error from the innermost "Types of property X are incompatible" line outward. That nested line names the actual mismatch.
  2. For missing declarations, try npm i -D @types/<pkg> first; if none exists, write a minimal .d.ts rather than reaching for any.
  3. Narrow rather than assert. A type guard, an in check, or an early return preserves safety where as discards it.
  4. Use tsc --noEmit --pretty to check the whole project; editors sometimes use a different TypeScript version than the build.
  5. Check strict, skipLibCheck and moduleResolution in tsconfig when errors appear only in CI or only in the editor.

Tools worth reaching for

  • tsc --noEmit
  • ts-node / tsx
  • @types/* packages
  • typescript-eslint
  • editor TS version selector

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

typescriptlang.org

Related TypeScript errors

See all 19 TypeScript errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.