You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
What happened to --experimental-transform-types?聽#5153
So, as of v26, built-in TypeScript support is stable but limited to type stripping / erasable TypeScript syntax. If your code only needs inline types removed, you should be able to drop the flag. If your code uses TypeScript syntax that requires JavaScript generation, such as enum, parameter properties, runtime namespaces, or import aliases, Node.js will error and you鈥檒l need a third-party transpiler/loader such as tsx, tsc, etc.
I think this can be closed as answered unless you are seeing a different issue with erasable syntax.
Activity
musshiyaki commentedon May 31, 2026
Looks like this was an intentional semver-major removal in Node.js 26.
The v26 TypeScript docs history says
v26.0.0removed--experimental-transform-types:https://nodejs.org/api/typescript.html
The v26.0.0 release notes also list:
(SEMVER-MAJOR) module: remove --experimental-transform-typeshttps://nodejs.org/en/blog/release/v26.0.0
So, as of v26, built-in TypeScript support is stable but limited to type stripping / erasable TypeScript syntax. If your code only needs inline types removed, you should be able to drop the flag. If your code uses TypeScript syntax that requires JavaScript generation, such as
enum, parameter properties, runtime namespaces, or import aliases, Node.js will error and you鈥檒l need a third-party transpiler/loader such astsx,tsc, etc.I think this can be closed as answered unless you are seeing a different issue with erasable syntax.
GongT commentedon Jun 2, 2026
Yes I see the doc, I'm not sure if this feature will come back or not 馃