EC
TS2834
TypeScriptERRORNotableTypeHIGH confidence

Relative import paths need explicit file extensions in ECMAScript imports whe...

Production Risk

Build will fail; resolve before shipping.

What this means

A type-checking error (TS2834): Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.. This diagnostic is emitted by the TypeScript compiler when relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path..

Why it happens
  1. 1Incorrect TypeScript syntax or type usage
  2. 2Type mismatch between declared and actual value
How to reproduce

TypeScript compiler reports TS2834 during type checking.

trigger — this will error
trigger — this will error
// Triggers TS2834
// Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.

expected output

error TS2834: Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.

Fix

Address the TypeScript diagnostic

WHEN When this error is reported by the compiler

Address the TypeScript diagnostic
// Run the TypeScript compiler for details:
npx tsc --noEmit
// Use the TypeScript playground to test your code:
// https://www.typescriptlang.org/play

Why this works

Review the full error message and location; the TypeScript handbook provides guidance on each error category.

Sources
Official documentation ↗

TypeScript Compiler Diagnostics

Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev

← All TypeScript errors