Version Details and Security Vulnerabilities

📦

joi

17.11.0

Comparision Betweeen 17.11.0 and 17.10.2

Identify the differences between the current version of the package and the previous one.

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

521.27 KB

519.94 KB

Version 17.11.0 Details

Joi 17.11.0 is a minor release focusing on refinements and incremental improvements over the previous stable version, 17.10.2. While the core functionality of object schema validation remains consistent, developers should note the difference in unpacked size of the package, 533785 bytes vs 532421 bytes. This suggests internal code or asset updates, potentially encompassing bug fixes, performance enhancements, or documentation adjustments. Analyzing the changelog accompanying this release will give specific details.

Both versions share identical dependencies, including @hapi/hoek, @hapi/topo, @sideway/address, @sideway/formula, and @sideway/pinpoint, indicating no API breaking changes to the libraries Joi depends on. Similarly, the developer dependencies used for testing and building, like @hapi/lab, @hapi/code, and typescript, remain consistent, ensuring a stable development workflow. The license remains BSD-3-Clause, and the repository location on GitHub is unchanged.

The key difference lies in the release date, with 17.11.0 published on October 4, 2023, after 17.10.2 released on September 17, 2023. Current npm package users should consider upgrading to benefit from potential bug fixes and performance improvements included in the latest 17.11.0 version. The semantic versioning guarantees no major backward compatibility issues between minor releases thus offering a risk-free upgrade. Always consult the official Joi release notes for a comprehensive list of changes.

Security Vulnerabilities

This site is an independent open-source project and is not affiliated with, endorsed by, or sponsored by npm, Inc. or GitHub, Inc. The name “npm” is a registered trademark of npm, Inc., used here solely to describe compatibility and reference publicly available npm package data.