Andrew Bradley

You can use the version of ng-ckeditor in my pull request, which will make your original code work unmodified. Alternatively, you can modify your code so that you assign the...

Historically I use version sniffing for this stuff, so I'd go with that. It's happened several times before that ts-node needs to implement multiple behaviors depending on the version of...

Thanks, I haven't had a chance to take a look yet, but WRT the double-typechecking: I imagine it would happen when mixing CJS and ESM. E.g. you have some `.mts`...

If double-typecheck is happening, the only visible side-effect would be higher CPU usage. So it's not a problem, per-se, it just means potentially a performance regression on node 20. If...

The scenario above could also happen if `entrypoint.mts` does `import './other.cts'` which does `import './another.cts'` (secretly compiles to `require('./another.cts')` So could happen in a mixed CTS / MTS codebase where...

The ideal until node supports CJS-via-loaders is that we use the message port to delegate all compilation into the loader thread. `service.compile()` in the main thread and all worker threads...

Does `diagnostics_channel` support blocking calls across thread boundaries? So that `require('./something.ts')` can be compiled off-thread? > since it means putting more logic in the sloppy mode string-literal code I'm not...

For the sake of anyone else reading along: A combination of `MessageChannel` & `SharedArrayBuffer` & `Atomics` can be used to make blocking RPC calls between threads. The goal is to...

What guarantees does `register()` make about import calls passing to the newly-registered loader? `register(a); await import(b)` which loaders handle the import of b?

Have `worker_threads` been considered? They incur less overhead than spawning external processes, and you can use something like [comlink](https://github.com/GoogleChromeLabs/comlink) for simple communication between worker and leader thread. It is *technically*...