-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hapi v17 Support #3
Comments
@timcosta acknowledged 👍 |
any updates? |
Working on it this morning should be good to go no later than Wednesday. |
@ar4mirez was this ever finished? If not, I'd be more than happy to help out |
@jamesdixon Hi sorry I've been busy lately, I'll be grateful if you can give me a hand with this one :D I'm trying to also update other one also working with hapi 17. Thank you 👍 |
Thanks to @jamesdixon ! 👍 this issue is now closed. |
@ar4mirez you're welcome! thanks for creating this in the first place! |
@jamesdixon thanks :D btw I fixed the issue with v8 and v9 it was just a problem with travis-ci 👍 |
Overview
If you are not aware yet, Hapi v17 is making the transition from callbacks to
async
/await
, as well as deprecating some other rarely used functionality. This is a breaking change that may make your plugin no longer compatible with the Hapi API.Changelog
Draft release notes can be found here: hapijs/hapi#3658
Target Release
The target release date for v17 is the beginning of November.
Tasks
async
/await
compatible using thev17
branch from Hapi for testingPossible dev flow for updating
npm link
within the Hapi reponpm link hapi
within your plugin repov17
of Hapi branch for testsnpm
. Please use a major version increment as this will be a breaking change and it would be terrible for it to sneak into current versions of Hapi.Notes
<8.0.0
.v16
will continue to be supported for as long as there exists a Node LTS actively being supported that is not compatible withv17
.The text was updated successfully, but these errors were encountered: