Summary

hapi v20.0.0 is a small release with few code changes. The major version bump is due to a change in project leadership and governance. The @hapi/joi dependency has also been replaced with @hapi/validate. Finally, hapi v20 is now tested on Node 14 in Travis CI.

• Upgrade time: low - none to a couple of hours for most users
• Complexity: low - requires following the list of changes to verifying their impact
• Risk: low - small number of changes with simple ways to retain previous behavior in most cases
• Dependencies: low - existing plugins will work as-is

Breaking Changes

• Eran Hammer has stepped down as the hapi lead maintainer. A group of former maintainers has stepped up to take over the project, and has formed a Technical Steering Committee (TSC) to govern the project (The future of the hapi project, a prelude #4111, The future of the hapi project #4113, Commercial License #4114).

New Features

• An isInjected property has been added to the request object to indicate if the request was created via the inject() method (Implement isInjected read-only request property to indicate request… #4117).

Bug fixes

• Content-Type response headers whose value is null are no longer sent (headers: avoid sending null content-type #4134).
• The server timeout and the payload timeout are no longer required to be less than the socket idle timeout (Removing the route timeout validation #4123).

Other Notable Changes

• The @hapi/joi module and joi-specific dependencies have moved out of the hapijs GitHub organization. joi has been replaced by @hapi/validate, a slimmed down version of joi designed specifically for hapi's internal needs only. hapi will continue to support joi for users' validation purposes (Replace joi with validate #4115, Leaving @hapi and making new plans joi#2411).
• All core modules are now tested on Node 14, in addition to Node 12. This is in preparation for Node 14 entering Long Term Support (LTS) in October.

Migration Checklist

hapi v20 should largely be a drop-in replacement for current hapi v19 users. If you experience issues during the upgrade process, please open an issue.