6 ms·

Also the release that drops typescript transforms: https://github.com/nodejs/typescript/issues/51 https://github.com/nodejs/typescript/issues/51 (I’m not disag

by jauco 4mo ago

Also the release that drops typescript transforms: https://github.com/nodejs/typescript/issues/51 https://github.com/nodejs/typescript/issues/51 (I’m not disagreeing to remove it. It just took me a while to find out what happened to it)

pier25 4mo ago
Initially it didn't make sense to me... but it looks like type striping is really the way to go for future TS. There's the "types as comments" proposal[1] which could even land on browsers one day. I started using the erasableSyntaxOnly setting in my tsconfig to get ready for this. [1] https://tc39.es/proposal-type-annotations/ https://tc39.es/proposal-type-annotations/
- sexylinux 4mo ago
  At this point we should really prompt all the AI power in the world we have to create a TS replacement. It seems grotesque.
  - pier25 4mo ago
    Something that uses WASM probably has more chances to succeed given the massive effort/investment in the past decade to shift from JS to TS.