Version Details and Security Vulnerabilities

📦

joi

17.13.2

Comparision Betweeen 17.13.2 and 17.13.1

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

518.52 KB

518.48 KB

Version 17.13.2 Details

Joi, a popular object schema validation library for Node.js, recently released version 17.13.2, a minor update following version 17.13.1. Both versions maintain the same core functionality, providing robust tools for defining and validating the structure of JavaScript objects. Examining the package information reveals that the core dependencies remain identical, including @hapi/hoek, @hapi/topo, @sideway/address, @sideway/formula, and @sideway/pinpoint. Similarly, the development dependencies used for testing and building the library are unchanged.

The key difference lies in the dist section, specifically the unpackedSize. Version 17.13.2 has an unpacked size of 530965 bytes, compared to 530927 bytes in version 17.13.1. This suggests internal code adjustments or optimizations, possibly bug fixes, that have slightly altered the package's overall size. While seemingly minor, this change could contribute to improved performance or stability. Notably, the fileCount remains constant at 36 indicating that file structure hasn't changed. The most noticeable difference for developers is the release date: version 17.13.2 was released on June 19, 2024, while version 17.13.1 was released on May 2, 2024. This means that 17.13.2 incorporates all enhancements and corrections made in the code repository during those 6 weeks. Due to semantic versioning, a move from joi 17.13.1 to joi 17.13.2 would not break any existing code or require any major changes to implement. Developers should consider upgrading to the latest version (17.13.2) to benefit from any potential performance improvements, bug fixes, and the most up-to-date validation logic. When facing uncertainty, reviewing the changelog will assist in any decision-making.

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.