Version Details and Security Vulnerabilities

📦

unrs-resolver

1.11.0

Comparision Betweeen 1.11.0 and 1.10.1

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

44.53 KB

43.98 KB

Version 1.11.0 Details

UnRS Resolver is a Node.js library designed to enhance your project's module resolution capabilities, particularly in environments utilizing the Plug'n'Play (PNP) approach. Version 1.11.0 introduces subtle but crucial updates over its predecessor, version 1.10.1, primarily focusing on the bundled native bindings tailored for various operating systems and architectures. Both versions share the core functionality of providing a robust and efficient mechanism for resolving module paths, a critical aspect for modern JavaScript projects leveraging complex dependency trees. They also share the same dependency for "napi-postinstall," ensuring compatibility with Node.js's Native API.

The most notable distinction lies within the optionalDependencies section. While both versions include a comprehensive list of pre-built binaries for platforms like Darwin (macOS - x64 and arm64), FreeBSD, WebAssembly (WASI), Android (arm64 and arm-eabi), Linux (various architectures including x64, ARM, PPC64, S390x, RISC-V), and Windows (x64, ia32, arm64), each binding in version 1.11.0 is updated to version "1.11.0", aligning with the main package version. In version 1.10.1, these bindings were correspondingly at version "1.10.1". This nuanced version bump in the native bindings likely addresses specific bug fixes, performance improvements, or security patches within those platform-specific components. A minor increase in the unpacked size from 45033 to 45603 bytes supports this, suggesting code improvements rather than major architectural changes. Ultimately, upgrading to version 1.11.0 grants developers access to the latest refinements in platform-specific native code, ensuring optimal module resolution across diverse deployment environments.

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.