Andrew Bradley

If I understand correctly, this relies on `Promise.race` and `context.cancelled` both being native `Promise` code? It seems like a promise polyfill could not avoid a memory leak, since `Promise.race()` would...

I thought about some API ideas to achieve "disposal" of cancellation listeners to avoid memory leaks. ## A Add helper method to register `onCancelCallback`, run `asyncWorkFunction`, and unregister the callback...

I've responded with a tiny, tested, working fix in https://github.com/TypeStrong/ts-node/discussions/1507 but no one has followed up. So the traction issue appears to be external to ts-node.

Visual Studio Code knows how to launch additional instances of itself, since it does this every time you test an extension in development. (see `execPath` in launch.json) Can you use...

@jacksleight What `$PATH` is Alfred giving to VSCode? If you configure Alfred to run a script saying `echo $PATH` what do you see? How is `node` added to your $PATH?...

Alfred isn't launched via bash, so it's not getting any of your path changes from .bashrc. I'm pretty sure there's another mechanism you need to use to setup environment variables...

It may help to locate the error messages being logged from this function: https://github.com/golf1052/code-sync/blob/master/src/helpers.ts#L123-L142 ...and share them here. @pingvinen @gildas

I see mts and cts file extensions were not mentioned above. This is evidence in favor of allowing users and customization hooks to specify.

Something else to consider: will node support a single flavor of globbing, or will it support multiple behaviors via options, similar to bash's various `shopt`s: `dotglob`, `extglob`, etc? I'm guessing...

We should also consider if an equivalent to this pseudo-code makes sense: `require('node:test').runDashDashTest(['pathA', 'pathB'])` Equivalent to the behavior of the `--test` flag. Understanding that yeah, `--test` spawns child processes already....