type-stripping in Node.js recommendations?

[marcomuser]

Node.js is adding native ts support. It would be great if the Node.js tsconfigs would follow the official recommendations: https://nodejs.org/docs/latest/api/typescript.html#type-stripping

[orta]

I think we'd need a separate one for that, the type-stripping in node is experimental and requires flagging

[jakebailey]

I'm not sure those are options that one should be enabling without understanding what you're doing already; those flags are also incomplete until TS adds the ability to block bad syntax and require .ts in imports as well.

[marcomuser]

A separate tsconfig sounds reasonable! Would you then wait for the tsconfig option mentioned (reference for others: microsoft/TypeScript#59601), or could we go ahead and provide a “strip-types” tsconfig that could be kept in sync with the Node.js recommendations for this mode going forward?

[kachkaev]

TypeScript 5.8 beta was just released with a new erasableSyntaxOnly option:
https://devblogs.microsoft.com/typescript/announcing-typescript-5-8-beta/#the---erasablesyntaxonly-option

It'd be great to see erasableSyntaxOnly as part of @tsconfig/strictest.

[vladshcherbin]

Would be so nice to have a config with nodejs recommendations and erasableSyntaxOnly

[kachkaev]

TypeScript 5.8.2 is out!
https://devblogs.microsoft.com/typescript/announcing-typescript-5-8/

What are the downsides of adding erasableSyntaxOnly to @tsconfig/strictest?

[jakebailey]

They have nothing to do with type error level strictness, and only about limiting the syntax to be able to run in type-erasing transformers (Node's amaro, ts-blank-space). People might be pretty unsatisfied if they're using enums, namespaces, etc.

There's a config mixin for this in #293 though, if you want it (wasn't linked here, oops).

[kachkaev]

Oh I did not know about @tsconfig/node-ts. Great stuff! I believe that this issue can be closed as resolved (in #293).

[vladshcherbin]

Would be nice to see this config mixin in readme table of contents otherwise the issue is resolved. Thank you!

[jakebailey]

Sent #297.