Version Details and Security Vulnerabilities

📦

unrs-resolver

1.6.0

Comparision Betweeen 1.6.0 and 1.5.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

20.08 KB

19.99 KB

Version 1.6.0 Details

UnRS Resolver has released version 1.6.0, building upon the foundation laid by the previous stable version 1.5.0. Both versions focus on providing a Node API for UnRS resolution with Plug'n'Play (PNP) support, aimed at developers seeking efficient and flexible module resolution within their projects. One key difference lies in the description field, which evolves from "Oxc Resolver Node API with PNP support" in version 1.5.0 to "UnRS Resolver Node API with PNP support" in the latest 1.6.0 -- potentially indicating a refined focus or rebranding effort.

A core aspect of both versions is the inclusion of numerous optional dependencies, with each dependency being a platform-specific binding like @unrs/resolver-binding-darwin-x64 for macOS x64 architecture or @unrs/resolver-binding-linux-x64-gnu for Linux x64 with GNU. These bindings are versioned alongside the main package, ensuring compatibility and optimized performance across various operating systems and architectures, demonstrating a commitment to broad platform support. The upgrade to 1.6.0 ensures that developers receive the most recent bindings, potentially benefiting from performance enhancements or bug fixes tailored to their specific environment.

Furthermore, version 1.6.0 introduces a dependencies field and specifies that it depends on napi-postinstall. Another change between the specified versions is in the funding field. Version 1.5.0 has a nested object with the url key, and version 1.6.0 contains only the url in plain text. Finally, the dates must be wrong, as the newest version has a date later than today and a week after the previous stable version.

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.