Wesley Wigham

Oh, neat, we already supported `--strict null` and the like, just not `-p null`. Neat. Small change to add it.

And as for the concern about buildinfos, I put together a harness that could actually test [multiple consecutive invocations](https://github.com/microsoft/TypeScript/commit/bc301f6bd477a9dbed9b7ae05ca9ccbbad80e47f) - looks like we handle the file list changing entirely just...

> Add an option to enable/disable package.json exports  I think a very important question for this is: With what default conditions (configurable?) and what behavior for the import/require conditions? Each...

Also, an important concern for declaration emit is cross-resolution mode compatibility. `node` and `node16` are often close enough that we can gloss over the differences in DT, but with more...

Also ref https://github.com/microsoft/TypeScript/pull/29353 where I did what I thought would be some minimal _emit_ changes to create a mode about as flexible as bundlers were at the time. That didn't...

For anything actually running TS in `node` at runtime, I think it'd have to be `node16` + `noEmit` allowing direct `.ts` references.

> I do have some concerns with the approach of enabling .ts extensions without its own flag. Maybe over time noEmit could imply that, the same way that checkJs implied...

While this works because tslib is fairly stateless, I think it's a bad idea because it loads two copies of every helper function into any node program that ends up...

The other option would be to use the `node` condition instead of `import` (or alongside), so `vite` falls back to a different entry point. (But seriously, why don't they use...

Yeah, the more I think about it, the more I'm convinced that we should just slam a `node` condition into the map that uses the existing `import` entry point, so...