| ▲ | hootz 6 hours ago | |||||||||||||
That is type stripping and is incompatible with syntax that requires transpilation, so it is not native TypeScript support. | ||||||||||||||
| ▲ | jazzypants 6 hours ago | parent | next [-] | |||||||||||||
TypeScript is a wide umbrella. For instance, Experimental Decorators are shunned by many (including me), but they are still used by millions. If I don't use any syntax that requires transpilation, am I not still using TypeScript? Now that we have `satisfies` and `as const`, there's really no reason to ever use an enum. In my opinion, TypeScript is best when it is simply used as Language Server, and it should never have had runtime implications in the first place. | ||||||||||||||
| ▲ | alanning 6 hours ago | parent | prev | next [-] | |||||||||||||
Node v22.7.0 added support for TypeScript syntax that requires transformation: `node --experimental-transform-types example.ts` As for whether this matches your definition of "native support" or not... | ||||||||||||||
| ▲ | ifwinterco 6 hours ago | parent | prev | next [-] | |||||||||||||
Isn't that mostly just enums? Is there anything else that doesn't run as valid JS if you strip the types (and maybe some other extra keywords)out? Genuine question, in my head there's not much, but TS has a few weird corners I maybe haven't used | ||||||||||||||
| ||||||||||||||
| ▲ | silverwind 5 hours ago | parent | prev [-] | |||||||||||||
Modern Typescript does not need runtime features. | ||||||||||||||
| ||||||||||||||