You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The target release date for v17 is the beginning of November.
Tasks
Reply to this to acknowledge that you are actively maintaining this module and are willing to update it
Update plugin to be fully async/await compatible using the v17 branch from Hapi for testing
Possible dev flow for updating
Clone Hapi
npm link within the Hapi repo
npm link hapi within your plugin repo
Your plugin will now be using v17 of Hapi branch for tests
Release new major version of your plugin on npm. 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
Support is being dropped for all versions of Node <8.0.0.
Hapi v16 will continue to be supported for as long as there exists a Node LTS actively being supported that is not compatible with v17.
Targeted release date is November 1st, 2017. Please try to have your plugin updated before then.
This issue is being opened because your plugin is listed on the official hapi website
The text was updated successfully, but these errors were encountered:
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: