We have unflagged `--experimental-strip-types` in v23.6.0. Here what I think are some of the next steps: - [x] Article on how to publish a new package @JakobJingleheimer https://github.com/nodejs/nodejs.org/pull/7279 - [x] Update SWC with https://github.com/swc-project/swc/pull/9846 and Amaro so we will be able to identify when ts syntax is unsupported (like enums in strip types) or just generally invalid syntax. This should be the last *"planned"* breaking change since it will throw different errors rather than [`ERR_INVALID_TYPESCRIPT_SYNTAX`](https://nodejs.org/api/errors.html#err_invalid_typescript_syntax) for everything. - [x] Backport the changes to v22 https://github.com/nodejs/typescript/issues/37 - [x] Wait for TypeScript 5.8 (at least beta) [`--erasableSyntaxOnly` flag](https://github.com/microsoft/TypeScript/issues/59601) - [x] Update the suggested tsconfig file with the new [`--erasableSyntaxOnly` flag](https://github.com/microsoft/TypeScript/issues/59601) @khaosdoctor (https://github.com/tsconfig/bases/pull/293) - [x] Create an utility (like https://github.com/fastify/tsconfig) to validate tsconfig or generate tsconfig compatible with `--experimental-strip-types` @robpalme added it to https://github.com/tsconfig/bases/blob/main/bases/node-ts.json - [x] Move the feature to stability 1.2 (Release candidate) - [x] Move to stable ideally around October 2025 when we cut v24 LTS release (this mean rename flags to --strip-types, remove warnings etc...) Feel free to add items if you think I missed something
We have unflagged
--experimental-strip-typesin v23.6.0.Here what I think are some of the next steps:
ERR_INVALID_TYPESCRIPT_SYNTAXfor everything.--erasableSyntaxOnlyflag--erasableSyntaxOnlyflag @khaosdoctor (Add recommended configuration for Node.js running TS natively tsconfig/bases#293)--experimental-strip-types@robpalme added it to https://github.com/tsconfig/bases/blob/main/bases/node-ts.jsonFeel free to add items if you think I missed something