Version Details and Security Vulnerabilities

📦

mime

2.4.6

Comparision Betweeen 2.4.6 and 2.4.5

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

56.21 KB

56.61 KB

Version 2.4.6 Details

Mime version 2.4.6 introduces subtle yet potentially impactful changes compared to the preceding 2.4.5 version. Primarily, the crucial update lies in the repository URL within the package metadata. Version 2.4.6 correctly points to git+https://github.com/broofa/mime.git, aligning with the current official repository. In contrast, version 2.4.5 erroneously references git+https://github.com/broofa/node-mime.git, highlighting a correction within the package's administrative details.

Beyond the repository fix, a minor difference is observed in the dist section. The unpackedSize differs slightly: 57564 bytes for version 2.4.6 compared to 57965 bytes for version 2.4.5. This hints at internal code or documentation adjustments impacting the package's overall size after extraction. Both versions, however, maintain a fileCount of 10, suggesting no additions or removals of files.

Developers leveraging the mime library should note these differences, particularly those relying on automated tools or scripts parsing package metadata for repository information. While the core functionality, described as "A comprehensive library for mime-type mapping", remains consistent across versions, the corrected repository link ensures proper package management and contribution workflows. The releaseDate indicates that version 2.4.6 was published approximately 26 days after version 2.4.5, suggesting a focused effort on addressing the repository URL issue promptly. Both versions share identical development dependencies, including popular tools like chalk, mocha, eslint, and standard-version, crucial for testing and maintenance, solidifying a stable development environment for the mime package.

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.