TS import type vs import — Runtime Value Missing

Diagnose runtime errors when using import type for a value that is needed at runtime, or vice versa, causing missing references.

beginnerdebuggingtsphase-16

Symptoms

A type-only import is used in a value position, or a value import is elided by TypeScript.
Error message: error TS1345 or runtime ReferenceError: X is not defined
Failure occurs intermittently or after a specific code path

Possible causes

import type is used but the symbol is referenced as a value (e.g., in a decorator or enum).
TypeScript elides imports that appear type-only, removing the runtime import.
Environment or runtime version mismatch introduces the defect

Diagnosis steps

Reproduce the error in a minimal isolated test case

node -e "require('./repro')"

Interpretation

If the minimal case reproduces, the bug is in the logic itself, not the environment. If not, collect environment details.

Capture the full error stack trace and identify the originating line

Set NODE_OPTIONS=--stack-trace-limit=100 and run with verbose logging

Interpretation

The first frame in user code is the trigger. Compare against the expected execution path to find the divergence point.

Inspect the values of all variables at the failure point

Add console.log / debugger / breakpoint at the line before the throw

Interpretation

Check for undefined, null, wrong type, or unexpected shape. The error message tells you what was wrong; the variables tell you why.

Root cause

import type tells TypeScript the import is type-only, so it is erased at compile time; using the symbol as a value then fails at runtime.

Fix

Use a regular import for symbols needed at runtime; use import type only for pure types.

Risk note

Applying the fix without understanding the root cause may mask the symptom and introduce a different defect. Always verify with the reproduction case.

Verify the fix

Run the code and confirm the symbol is available at runtime; check the compiled output includes the import.

Symptom and Error Message

When running the TypeScript code, the runtime raises the following error:

error TS1345 or runtime ReferenceError: X is not defined

This error indicates that a type-only import is used in a value position, or a value import is elided by typescript. The error is reproducible and appears consistently once the triggering condition is met. In production, you may see this error sporadically because the triggering condition depends on runtime state that is not always present.

Root Cause Analysis

The fundamental cause is: import type tells typescript the import is type-only, so it is erased at compile time; using the symbol as a value then fails at runtime. Two factors converge to produce the visible error. First, import type is used but the symbol is referenced as a value (e.g., in a decorator or enum). Second, typescript elides imports that appear type-only, removing the runtime import. Either factor alone might not trigger the error, but together they create the conditions for failure.

Diagnosis Walkthrough

Start by reproducing the error in isolation. Strip away everything except the minimum code path that triggers the error. Once you have a minimal reproduction, inspect every variable at the failure point. Look for: undefined where an object is expected, wrong types, stale references, and off-by-one indices. The error message tells you what went wrong; the surrounding state tells you why.

Fix and Code Example

// Before (buggy)
// ... code that triggers the error ...

// After (fixed)
// ... corrected code with proper guard or type check ...

The fix addresses the root cause directly: use a regular import for symbols needed at runtime; use import type only for pure types. After applying the fix, the error no longer occurs because the triggering condition is either prevented or handled gracefully.

Verification

Run the code and confirm the symbol is available at runtime; check the compiled output includes the import. Run the reproduction case again and confirm the error is gone. Then run the full test suite to check for regressions. In production, monitor error logs for 24 hours to confirm the fix is effective under real load.

Common Pitfalls

A frequent mistake is to suppress the error with a try/catch or conditional without addressing the underlying cause. This masks the symptom but the defective logic remains, and the error will resurface in a different form. Always fix the root cause, not just the error message. Another pitfall is fixing the symptom only in the happy path while ignoring edge cases like empty input, null values, or concurrent access.