Roadmap to stable strip-types #24

We have unflagged --experimental-strip-types in v23.6.0.
Here what I think are some of the next steps:

• Article on how to publish a new package @JakobJingleheimer feat(learn): add article for publishing a typescript package nodejs.org#7279
• Update SWC with feat(ts/fast-strip): Distinguish invalid vs unsupported swc-project/swc#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 for everything.
• Backport the changes to v22 Unflagging Type Stripping in Node.js v22 #37
• Wait for TypeScript 5.8 (at least beta) --erasableSyntaxOnly flag
• Update the suggested tsconfig file with the new --erasableSyntaxOnly flag @khaosdoctor (Add recommended configuration for Node.js running TS natively tsconfig/bases#293)
• 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
• Move the feature to stability 1.2 (Release candidate)
• 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