Version Details and Security Vulnerabilities

📦

read-package-json

2.1.1

Comparision Betweeen 2.1.1 and 2.1.0

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

18.72 KB

18.39 KB

Version 2.1.1 Details

Read-package-json versions 2.1.1 and 2.1.0 offer robust solutions for parsing and validating package.json files, mirroring the functionality used internally by npm. Both versions share a core set of features, ensuring consistent handling of package metadata. They both provide the same dependencies with "glob":"^7.1.1", "graceful-fs":"^4.1.2", "normalize-package-data":"^2.0.0", "json-parse-better-errors":"^1.0.1".

However, a key difference lies in the dependencies: version 2.1.1 introduces npm-normalize-package-bin with version "^1.0.0", while version 2.1.0 depends on slash at version "^1.0.0". This suggests a shift in how the package handles bin entries within the package.json file. The newer version uses npm-normalize-package-bin which is dedicated to specifically normalizing the bin entries.

While both versions maintains consistent developer tooling using tap for testing and standard for code linting, version 2.1.1 has a slightly larger unpacked size (19171 bytes) compared to version 2.1.0 (18828 bytes), likely due to the inclusion of the new dependency. Developers utilizing read-package-json should consider this change and asses if npm-normalize-package-bin better suits their needs for handling the bin entries of the package.json. Both versions are licensed under ISC and maintained in the npm/read-package-json repository and authored by Isaac Z. Schlueter.

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.