Node.js marks built-in TypeScript type‑stripping stable (v25.2.0)

Node.jsTypeScriptTooling

Key update

Node.js v25.2.0 (released Nov 11, 2025) marks the built‑in TypeScript "type stripping" transformer as stable, formally making it a supported runtime feature so you can execute many .ts files directly with node (e.g., node file.ts) without an external transpiler or loader. (nodejs.org)

Why it matters

This is a practical simplification for many developer workflows: quick scripts, CI helpers, small CLIs and routine automation can often be run without adding ts-node / swc / Babel / a build step, reducing friction and dependency surface area. It also narrows the gap between Node and other runtimes that already supported direct TypeScript execution.

Important constraints you must treat as part of any adoption decision: the runtime performs lightweight type stripping (no type checking), intentionally skips features that require JS code generation, and does not honor tsconfig transformations or accept TypeScript inside node_modules. For production builds, libraries, or code that relies on full compiler semantics (declaration emit, path aliases, enums, etc.), continue using a proper compile step or a dedicated tool (tsx, tsc, bundlers). Practically, adopt incrementally: standardize your CI/build for released artifacts, use native type‑stripping for developer-facing scripts where its limitations are acceptable, and pin Node versions in CI to avoid runtime differences.

Source

Read Next