Version Details and Security Vulnerabilities

📦

joi

17.13.3

Comparision Betweeen 17.13.3 and 17.13.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

518.67 KB

518.52 KB

Version 17.13.3 Details

Joi, a popular object schema validation library for JavaScript, recently released version 17.13.3, a minor update following closely after version 17.13.2. Both versions maintain identical core dependencies, including @hapi/hoek, @hapi/topo, @sideway/address, @sideway/formula, and @sideway/pinpoint, ensuring consistent functionality for developers already relying on these components. Similarly, the development dependencies, vital for testing and building the library, remain unchanged, featuring @hapi/lab, @hapi/code, typescript, @types/node, @hapi/bourne, and @hapi/joi-legacy-test. The license continues to be BSD-3-Clause, and the repository URL remains the same on GitHub.

The primary difference lies within the distributed package itself. Version 17.13.3 exhibits a slightly larger unpacked size of 531117 bytes compared to version 17.13.2's 530965 bytes, suggesting minor alterations or optimizations within the codebase. The fileCount remains constant at 36. Furthermore, the release dates indicate a newer build for 17.13.3, issued on June 19, 2024, at 15:18:03 UTC, subsequent to 17.13.2 which was released earlier that day at 09:21:36 UTC.

For developers, this update likely includes bug fixes, performance enhancements, or other minor improvements that don't warrant a major or minor version bump. While the changes might be subtle, upgrading to the latest version is generally recommended to benefit from the most recent refinements and ensure compatibility with evolving JavaScript environments. Developers leveraging Joi for robust input validation in applications, APIs, or configuration management should consider this incremental upgrade.

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.