Stephen Haberman

Cool, that makes sense. Thanks for the insight!

We really need something like this because sometimes our connection pool ends up in an `toEqual` and it OOMs/blows up (specifically when a failed assertion tries to do a expected/actual...

Fwiw I've confirmed that, per my recollection, ts-node-dev (via node-dev itself afaiu) is able to restart and have the debugger seamlessly reconnected. It looks like this was fixed in node-dev...

Maybe it's because node-dev uses child_process.fork? https://github.com/fgnass/node-dev/blob/5d07f002cb9288450ebea1dcc9f60205c958897c/lib/index.js#L117

Just a note of progress, I poked at this a little bit over the weekend and noticed that in a small/tiny app, with tsx watch+inspect and a single `index.ts` file,...

Hey @dunckr ! Thanks for the hint; just curious, was your `await server.close()` fixing "port in use errors" on like your express/fastify/etc port 3000 or 4000 or what not, or...

I've been working with the latest releases, and it seems like https://github.com/esbuild-kit/tsx/pull/116 fixed this! I'm able to see `tsx watch` pick up reloads while connected with a debugger and everything...

Hey @dankeboy36 , ah yeah, that sounds like a good idea. If you could submit a PR, that'd be great!

:tada: This issue has been resolved in version 1.127.0 :tada: The release is available on: - [npm package (@latest dist-tag)](https://www.npmjs.com/package/ts-proto/v/1.127.0) - [GitHub release](https://github.com/stephenh/ts-proto/releases/tag/v1.127.0) - `v1.127.0` Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:

Hey @zakhenry ; cool, that makes sense. Fwiw I haven't really thought much about what a cancellation API would look like. If you'd like to work up a proposal and...