Guillaume Quittet

@bradennapier > I do not appear to get any registrations for live or ready -- i registered an onRoute before it and nothing happened either. Same answer as above, it's...

Here is my simple working example with Node 18 and Fastify 4 It does not work with Node 14/16 and Fastify 4 but it's working with Node 14/16 and Fastify...

I found the commit that breaks the compatibility with Fastify 4 and Node 16/14 👍 [f0281948cfcb04cd1c5c93a330823278e4a1b44f](https://github.com/fastify/fastify/commit/f0281948cfcb04cd1c5c93a330823278e4a1b44f) I will debug this commit later and make a pull request on the Fastify...

OK I understand the issue, Fastify by default is listening on IPv4 and IPv6 at the same time using a workaround with 2 servers. https://github.com/fastify/fastify/issues/3536 But when you use fastify.server...

I have updated the documentation on my side : https://github.com/gquittet/graceful-server#fastify 🙂

@arsenal120496 It's normal. It's because of https://schedule.readthedocs.io/en/stable/examples.html?highlight=day#run-all-jobs-now-regardless-of-their-scheduling You have to use `schedule.run_pending()` instead of `schedule.run_all()`

Hello @StepanMynarik 👋 Thank you for your interest in the project. I will check what I can do to improve the DevX with ESM and Graceful Server 👀

Hello @StepanMynarik 👋 Just a quick update, I will work on this issue this week 👍 If you have a simple example of the issue, share it with me 😉...

Hello @StepanMynarik 👋 Now Graceful Server is ESM ready! 🎉 I close the issue

Sorry for that, everything is working fine with version `5.0.2` I just published it 🚀 I switch from `webpack` to `tsup` and it was a pain in the *** for...