The future of `--experimental-transform-types` · Issue #51 · nodejs/typescript · GitHub
//voltron/issues_fragments/issue_layout" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
//voltron/issues_fragments/issue_layout;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
nodejs
typescript
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star<br>116
The future of --experimental-transform-types #51
New issue<br>Copy link
New issue<br>Copy link
Closed
Closed<br>The future of --experimental-transform-types#51
Copy link
Description
marco-ippolito<br>opened on Jan 27, 2026
Issue body actions
I wanted to talk about the future of --experimental-transform-types.
The feature has been stable for a while no outstanding issue.
The problem with this flag is that the syntax supported might change due to typescript deprecations (rip module which btw is already not supported just an example), syntax becomes supported in the js spec (Maybe enums one day 😆) etc...
Here a few options:
remove the flag completely (I dont know if its even possible given the massive usage)
Leave the flag experimental forever (I dont like this option)
Mark the flag as stable but document that the changes in the syntax are not semver major therefore it can break)
Mark the flag as stable and mark every syntax change as semver major (😫)
WDYT @nodejs/typescript
Reactions are currently unavailable
Metadata<br>Metadata<br>Assignees
No one assigned
Labels
No labelsNo labels
Type
No type
Fields<br>Give feedback
No fields configured for issues without a type.
Projects
No projects
Milestone
No milestone
Relationships
None yet
Development
No branches or pull requests
Issue actions
You can’t perform that action at this time.