Closed alexb-uk closed 4 years ago
Actually above should read "Started refactoring to use async / await to aid readability" there is still a lot of "then's" to be updated.
It seems like the project has been quiet for a while now.
Could a maintainer confirm if they still have time to work on this project? If not I'll look into publishing my fork on NPM and will try to keep it up to date. This library has been really useful for me so would be a shame for it to drift away.
Thanks
Hi Alex, I apologize.
Day job and life have kept me pretty busy. We still have not upgraded to hapi 17 at my company because of the massive rewrite it requires.
Thank you so much for the effort you have put into this library. I am definitely interested in moving it forward. I will set aside some time this week to get rolling on v17 support as well as some other ideas I have.
Thanks again, Brad
Sent from my iPhone
On Oct 23, 2018, at 4:02 AM, Alex notifications@github.com wrote:
It seems like the project has been quiet for a while now.
Could a maintainer confirm if they still have time to work on this project? If not I'll look into publishing my fork on NPM and will try to keep it up to date. This library has been really useful for me so would be a shame for it to drift away.
Thanks
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
Any status change on getting support for v17 merged in?
Closing as Hapi is now on version 19 and also this PR now have merge conflicts.
Ref: Issue Hapi v17 Support #103
Changes include: