Version Details and Security Vulnerabilities

📦

joi

17.6.4

Comparision Betweeen 17.6.4 and 17.6.3

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

512.64 KB

Version 17.6.4 Details

Joi 17.6.4 is a minor version update to the popular JavaScript object schema validation library, building upon the foundation established in version 17.6.3. Both versions share the same core dependencies, including @hapi/hoek for utility functions, @hapi/topo for topological sorting, @sideway/address for address parsing, @sideway/formula for formula evaluation, and @sideway/pinpoint for pinpointing issues. These dependencies ensure a robust and reliable validation process. Similarly, development dependencies like @hapi/lab for testing, @hapi/code for assertions, typescript for type checking, and @types/node for Node.js typings remain consistent, indicating a shared development and testing environment.

The primary difference lies in the release date and potentially subtle bug fixes or performance improvements. Joi 17.6.4 was released on October 22, 2022, while 17.6.3 was released on October 11, 2022. Developers should upgrade to the latest version (17.6.4) to benefit from these improvements and ensure they are using the most secure and stable version of the library. The unpacked size is lightly different (524942 vs 524947) which indicates that some very small changes were introduced with the new release.

Joi is crucial for developers seeking to enforce data integrity in their applications. By defining schemas, developers can easily validate JavaScript objects against predefined rules, preventing errors and ensuring data consistency. Joi's clear and expressive API makes it easy to define complex validation rules, including data types, required fields, and custom validation logic. The BSD-3-Clause license allows for flexible use in a variety of projects.

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.