Node.js Merges Native TypeScript Support in Latest Alpha Release
After years of community debate and increasing pressure from rival runtimes, the Node.js core team has officially merged native TypeScript execution into the master branch. The feature debuted today in the version 26.0.0-alpha.1 release, marking a fundamental shift in how developers interact with the server-side JavaScript ecosystem.
Historically, developers wanting to run TypeScript in Node.js were forced to rely on external build steps—such as `tsc`, `esbuild`, or third-party execution wrappers like `ts-node`. This added significant overhead to CI/CD pipelines and complicated local debugging experiences. With this new pull request, Node.js can execute `.ts` files directly out of the box without any mandatory pre-compilation.
The implementation relies on a highly optimized "type-stripping" mechanism. Rather than performing full type-checking at runtime—which would severely degrade performance—the V8 engine utilizes a rapid parsing step to strip away TypeScript-specific syntax, executing the remaining code as standard JavaScript. Developers who want strict type-checking will still need to run their code through a dedicated linter or compiler before deployment.
"The reality is that TypeScript has won the ecosystem, but our tooling was still treating it like a second-class citizen," wrote Node.js core collaborator Marco Rossi in the PR summary. "Deno and Bun proved that zero-config TypeScript execution is what developers actually want. We are finally reducing the friction and modernizing the Node experience."
The decision to implement type-stripping over full compilation mirrors the widely discussed "Type Annotations" ECMAScript proposal, which aims to allow JavaScript engines to simply ignore type syntax as comments. By moving in this direction, Node.js is future-proofing its runtime against upcoming language standards.
While the feature is currently behind an experimental flag (`--experimental-strip-types`), the steering committee has indicated a strong desire to stabilize it ahead of the Node 26 LTS release scheduled for later this year.
Early benchmarks show that the native stripping process adds less than a 5% overhead to cold boot times compared to raw JavaScript execution, a massive improvement over traditional transpilation methods.