Version Details and Security Vulnerabilities

📦

uuid

3.4.0

Comparision Betweeen 3.4.0 and 3.3.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

33.47 KB

33.87 KB

Version 3.4.0 Details

Version 3.4.0 of the uuid package brings several updates compared to the prior stable version, 3.3.3, making it a noteworthy upgrade for developers relying on RFC4122 UUID generation. Primarily, the newer version demonstrates advancements in its development dependencies. Notably, eslint jumps from version 6.2.0 to ~6.4.0, reflecting a potential shift towards improved code linting and adherence to modern JavaScript standards. Furthermore, the @commitlint tooling sees a significant upgrade, moving from version 8.1.0 to ~8.2.0 for both @commitlint/cli and @commitlint/config-conventional, potentially streamlining commit message conventions and enforcing stricter code contributions.

Beyond dependency shifts, the package's details also show minor differences. While file count remains consistent at 19, the unpacked size has slightly decreased from 34683 bytes in version 3.3.3 to 34269 bytes in version 3.4.0, hinting at potential optimizations in code size. Another key difference is the repository URL. Version 3.3.3 points to github.com/kelektiv/node-uuid.git, while version 3.4.0 points to github.com/uuidjs/uuid.git, indicating a potential change in project ownership or repository management. Finally version 3.4.0 was released on "2020-01-16" almost 6 months later than version 3.3.3, released on "2019-08-19". Developers who value up-to-date tooling, stricter coding standards, and efficient package sizes should consider upgrading to version 3.4.0.

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.