Version Details and Security Vulnerabilities

📦

unrs-resolver

1.7.10

Comparision Betweeen 1.7.10 and 1.7.9

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.32 KB

20.3 KB

Version 1.7.10 Details

Unrs-resolver version 1.7.10 represents a minor update to the UnRS Resolver Node API, building upon the foundation established by version 1.7.9. Both versions cater to developers seeking a robust solution for resolving UnRS names within Node.js environments, enhanced with Plug'n'Play (PNP) support for seamless integration with modern package managers. Core functionalities remain consistent, meaning existing code likely won't require significant modifications for upgrading. The key difference lies in the optional dependencies which specify platform-specific native bindings. In version 1.7.10, these bindings (@unrs/resolver-binding-*) have been updated to version 1.7.10, reflecting potential bug fixes, performance improvements, or compatibility updates tailored to each targeted operating system and architecture (Darwin, FreeBSD, Linux, Windows, WASM).

The napi-postinstall dependency, crucial for building these native bindings during installation, remains unchanged, reassuring developers of a consistent build process. The dist metadata shows a slight increase in unpacked size from 20785 to 20804 bytes, suggesting minor code additions or adjustments in the newer version of platform binding, but this is really minimal. The update from version 1.7.9 to 1.7.10 ensures you're leveraging the latest optimisations and platform-specific enhancements for UnRS name resolution, particularly important for applications demanding the highest performance or those deployed across diverse environments, and contains a release date 2 days after the previous version. By selecting a specific optional dependency when installing this resolves automatically the compatibility issues under the targeted os.

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.