𝗡𝗼𝗱𝗲.𝗷𝘀 𝟮𝟰 𝗡𝗮𝘁𝗶𝘃𝗲 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁
Node.js 24 changes how you use TypeScript. You can now run .ts files in production without a build step.
The runtime removes type annotations at load time. It treats TypeScript as annotated JavaScript and executes it directly. This eliminates the need for transpilation or bundling.
Why this matters:
- You only need one source of truth.
- You remove the complexity of managing dist directories.
- Your development environment matches production exactly.
How it works: The module loader intercepts the source text. It strips interfaces, type annotations, and type-only imports. The remaining logic runs on the standard V8 engine. The transformed code stays in the module cache, so it only happens once per module load.
The limits you must know: This is not a full replacement for your build pipeline. You still need tools for certain tasks.
- No type checking: The runtime does not check for errors. You must run tsc --noEmit in your CI pipeline to catch bugs.
- No path aliases: It does not support tsconfig.json path mappings.
- No decorators: Advanced transformations still require a bundler like esbuild.
- No runtime safety: Stripped types provide zero protection at execution. Use libraries like Zod for data validation.
When to use it: Native TypeScript is perfect for microservices with simple dependency graphs. It increases deployment velocity by reducing moving parts.
When to stick to traditional builds: If you need aggressive optimization, tree shaking, or minification, keep your current pipeline. Large applications with complex build requirements will still benefit more from optimized JavaScript bundles.
How to set it up: To keep your stack traces readable, use the source maps flag.
Example command: node --enable-source-maps src/server.ts
This allows you to debug errors using your original TypeScript line numbers.