Rob Palmer

Today Node LTS supports `with` and Node Latest does **not** support `assert`. In three weeks, Chrome will also not support `assert`. - `assert` arrived in Chrome 92 _(2021-07-20)_ & Node...

Just to add to @RyanCavanaugh's list of reasons to add this mode: a further benefit not yet stated is that it will permit TypeScript (if the team wishes) to introduce...

Thanks for the clear concise comprehensive update, @RyanCavanaugh. ```ts namespace T { } // OK (type-only) ``` This was the only surprise to me. I appreciate it does not emit...

The [ts-blank-space](https://bloomberg.github.io/ts-blank-space/) compiler I mentioned [earlier in this issue](https://github.com/microsoft/TypeScript/issues/59601#issuecomment-2286741349) is now publicly available. One correction to the earlier post is that the performance multiplier relative to classic `ts.transpileModule` with `noCheck`...

The next step appears to be naming the flag. So here are some options. (Personally I mildly prefer `noTypeDrivenEmit`) # Node-centric - `stripTypes: true` - `stripTypesOnly: true` - `onlyStripTypes: true`...

I appreciate this fix will align the newer mode with the original intended behaviour. What are the chances this will be a breaking change for users of `"useDefineForClassFields"`?

The general answer is no, the work on Isolated Declarations does not change the expressiveness of declaration files. They are unrelated goals. Campaigning for that goal is best done on...

Isolated Declarations can be enabled in `tsconfig.json` in TypeScript 5.5 which was released two weeks ago.

nit: In the PR description the second code example does not match the preceding wording - it doesn't use `readonly`

It looks like you have this under control. I wanted to mention that `useDefineForClassFields: true` is the modern default in TypeScript and aligns with JS semantics. It gets automatically enabled...