The relative package, a small utility for resolving relative filepaths between any two paths, saw a minor update from version 3.0.1 to 3.0.2. Both versions share the same core functionality: accurately calculating relative paths whether you're moving from file-to-directory, file-to-file, directory-to-file, or directory-to-directory. This makes it a versatile tool for developers managing file structures within their projects.
The key difference lies in the dependencies. Version 3.0.2 introduces a production dependency on isobject, requiring version 2.0.0 or higher. While the reason isn't explicitly stated, it likely improves the robustness or accuracy of the relative path calculations, particularly in handling potentially atypical path inputs. Developers should be aware of this new dependency and ensure it's included in their project's dependency tree when upgrading.
Furthermore, the development dependencies also experience subtle changes. Version 3.0.1 uses mocha at version ^2.1.0 and should at ^5.0.0. Version 3.0.2 simply specifies '*' for both mocha and should, implying any version will work, or simply using the latest versions. This is mostly relevant for developers running tests or contributing to the relative package itself, as it affects the testing environment. The release dates highlights a more than 4 months gap which might indicate other non-functional changes. Choose the newer version for latest features and bug fixes.
The are not vulnerabilities for the version 3.0.2 of the package relative