@hapi/hoek is a Node.js utilities module intended for the hapi ecosystem, providing hapi-specific helper methods. It’s designed to work well with the hapi web framework and related components, but can also be used standalone or with other frameworks.
Project status
- The source (hapijs/hoek) appears to be actively maintained, with an upstream push on 2026-07-31 and a corresponding tagged update candidate (v12.0.0-rc.0).
- Update cadence looks bursty rather than steady, with the last clearly identified stable update in 2024-11-14 (v11.0.7) and then a new v12 release candidate in 2026-07-31 (roughly 19 months later).
AI summary generated
Recent updates
v12.0.0-rc.0
No release notes were provided for v12.0.0-rc.0. The diff information available shows a large structural change where the existing package entrypoints and most of the implementation/type files under lib/ are removed, suggesting a packaging or module-layout migration rather than a small incremental change.
v11.0.7
Release v11.0.7 contains no publisher-provided release notes. The code diff shows a targeted change in Hoek.clone() behavior for Error cloning using structuredClone, plus new tests covering Error instances with function properties.
v11.0.6
Release v11.0.6 was published on 2024-10-24, but the publisher did not provide release notes. Because no change log details are included, the specific new features, bug fixes, or breaking changes cannot be verified from the provided information alone.
v11.0.4
Release v11.0.4 makes a small packaging change to improve TypeScript type resolution. It updates the package.json exports map to explicitly reference the generated TypeScript declaration file for the package root export.
v11.0.3
v11.0.3 includes URL type support as stated in the release notes. The actual code changes in this diff are broader, adding new module formats/exports (ESM), introducing a new AssertError class, and changing some module resolution and exports behavior beyond what is documented.
Featuresv9.1.1
The release notes for v9.1.1 are not provided in the supplied data, so no specific user-facing changes can be confirmed from the publisher. To determine upgrade impact, you should compare v9.1.0 to v9.1.1 in the repository (release diff, commits, changelog history) and review any linked PRs for API, configuration, and dependency changes.