Matteo Collina

There is no need for any special `postMessage` here. The underlining problem is that sending 'SIGINT' does not emit the `'exit'` event. The following would log everything: ```js import {...

I'm reopening because I think I can do some magic to handle these.

Considering how Vercel or Netlify works, it's better to load the transport as a stream, and use it in the main process. You'll only have problems in using a different...

This would be an excellent transport to add! Would you like to publish it?

I think this is a good start. You should make sure tha the result of .compose() can be disposed. Also, docs are missing.

> I'm also confused about what 's after .the close() agent no longer accepts requests I agree, I think it should error at this point but not drop any current...

Thanks for reporting! Would you like to send a Pull Request to address this issue? Remember to add unit tests.

I think we can change this to: ```js const { files, values } = await req.saveRequestFiles(); ```

Yes, it seems we forgot about values in the design of that API.

@dzek69 well, that's well out of support anyway, there would never be a backport for fastify 3.x.