4 ms·
On a side note, I recently experimented with native TS support in Node.js and it felt like magic: no need for extra flags; debugging and watch just work; types
by Klaster_1 2y ago
On a side note, I recently experimented with native TS support in Node.js and it felt like magic: no need for extra flags; debugging and watch just work; types are simple to re-use between browser and server. Erasable syntax seems like the way forward, can't wait for it to land in browsers.
- normie3000 2y ago> can't wait for it to land in browsers Presumably for download size and backward compatibility everyone will still serve JS to browsers.
- eddd-ddde 2y agoBut it'd be nice not to /have to/. Specially when working on new projects with no build step.
- WorldMaker 2y agoTypescript Types don't add that much to download size and generally compress very well.
- madeofpalk 2y agoIt is really nice. I'm glad the Node and Typescript teams finally starting making pragmatic decisions to actually be useful. Now typescript just needs some better defaults from tsc --init to match :)
- Shacklz 2y agoSame here - it's really quite something. The future is looking good! That being said, there are currently still some hurdles. Necessity for explicit file-extensions in the imports is definitely the big offender (it's invalid typescript syntax without the allowImportingTsExtensions-flag). The trend is definitely clear though, most devs want ESM, most devs want types; it's just a matter of time until the ecosystem adapts. I suppose for types to finally land in the browser, TC39 will have to undergo the "progress is one funeral at a time"-principle, which will probably take another while.