Post

I've found that Explicit Resource Management is not well documented as unsupported. The `using` keyword requires code modification that breaks at runtime.

Since we are at Bluesky, one thing I noticed is that they use extension less imports in their TS code very extensively, and I am fairly sure this is quite common in the ecosystem github.com/bluesky-soci... - vite also does it AFAICT

I guess the use-cases that span both bundlers and Node TS are: 1. Making sure TS code written for Node is also compatible with bundlers (this grow-up case seems important) 2. Seeing if bundlers can output code that could run using Node's TS support (this layering case might have some value?)

2. Is important due to things like jsx and enum.

Does this unflag transform-types also or is that a separate story?

Please please please limit it to type stripping and make Node.js support in projects *the* argument to push back against the other nonsense.

does it mean nodejs do not support TS natively?

It does now with this flag, but previous you'd need extra tools like tsx

It just strips the types I believe, there’s another flag for supporting other parts of TS

also @ryanflorence.com because I couldn't find a Remix account.

FYI Remix & React Router Dev Rel @brookslybrand.bsky.social

We should maybe check this with Mocha @joshuakgoldberg.com? Or update documentation?