Andrew Bradley

Thanks, I'll have to give this some thought. It's a breaking change to use a child process for all users. It affects PIDs and signal handling and whatnot. And it's...

Only skimming the code, so I may have misinterpreted. But FWIW it's ok to make the breaking change to stop resolving entrypoint relative to our --cwd. Not sure if that...

Also feel free to push a long commit history, no need to force-push if you don't want to. We will squash merge it to `main` anyway.

Sounds good. FWIW I'm going to start merging breaking changes to `main`, so we're fully in breakage mode.

Thanks, can I get a quick bulleted list of the changes and their motivation, to assist review? In another comment, or by updating the issue description? `ts-node --esm` avoids loading...

I tracked this down to an issue with invalidating sourcemap cache in source-map-support. Without such an API, we can't tell source-map-support that it needs to fetch a new sourcemap from...

@blakeembrey yeah, that could work. Do you know, are non-`ts-node` sourcemaps kept in that cache? Would wiping the cache lead to a bunch of extra FS calls for `node_modules` which...

No need, superceded by the swc option. On Thu, Jun 16, 2022, 11:35 PM Roger Qiu ***@***.***> wrote: > Is there any progress on this? > > — > Reply...

I recommend checking out #1533 and submitting a pull request. It should solve your problem. #1533 has a low level of effort required for implementation, and I'm happy to answer...

The `--files` option might fix this, I'm not sure. https://typestrong.org/ts-node/docs/options https://typestrong.org/ts-node/docs/types