Version Details and Security Vulnerabilities

📦

unrs-resolver

1.3.3

Comparision Betweeen 1.3.3 and 1.3.2

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

19.84 KB

Version 1.3.3 Details

Unrs-resolver is a Node.js API designed to enhance Oxc Resolver functionality, especially within projects employing the Plug'n'Play (PNP) approach. Version 1.3.3 builds upon the foundation laid by version 1.3.2, primarily focusing on updates within its optional dependencies. Both versions share the same core functionalities, MIT license, repository on GitHub, and funding link via GitHub Sponsors. They even have the same number of files and unpacked size.

The key change lies in the specific versions of the optional @unrs/resolver-binding-* packages. In version 1.3.3, all these bindings are updated to version 1.3.3, while in 1.3.2, they are pegged to version 1.3.2. These bindings provide platform-specific implementations crucial for optimal performance. This update likely addresses bug fixes, performance improvements, or compatibility enhancements related to the underlying architecture bindings.

For developers, this means that upgrading from 1.3.2 to 1.3.3 ensures they are leveraging the latest compiled binaries tailored to their operating system and architecture. Staying current with these bindings is vital to guarantee optimal performance and prevent compatibility conflicts. Moreover, the "releaseDate" field indicates when the package was published on the npm registry. For version 1.3.3, it is "2025-03-29T18:17:48.347Z", and for version 1.3.2, it is "2025-03-26T19:41:14.459Z". Developers should consider this package if they need a performant and reliable resolver designed to work with PNP.

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.