@storybook/addon-links is a valuable tool for creating interconnected stories within your Storybook, enhancing the navigation and discoverability of your UI components. Examining versions 3.4.11 and 3.4.10 reveals a subtle yet crucial update. Both versions share a common lineage: they depend on the same core libraries like global, prop-types, babel-runtime, and peer dependencies react, react-dom, and @storybook/addons, ensuring that the fundamental functionality of linking stories remains consistent. The development dependencies, including react, enzyme, react-dom, and @storybook/react, also mirror each other, indicating a unified testing environment.
A key difference lies in the dependency @storybook/components. Version 3.4.11 relies on @storybook/components version 3.4.11, while version 3.4.10 depends on @storybook/components version 3.4.10. This suggests that the update in 3.4.11 primarily addresses bug fixes or feature enhancements within the component library used by the addon to build its UI elements rather than a substantial overhaul of the linking functionality itself. Another point to consider is the release dates, version 3.4.11 was released later than version 3.4.10 and this indicates that newer version contains bug fixes as usual because the rest of the data looks identical.. Developers should always prioritize using the latest stable version (3.4.11 in this case) to benefit from the most up-to-date improvements and fixes.
All the vulnerabilities related to the version 3.4.11 of the package
node-fetch forwards secure headers to untrusted sites
node-fetch forwards secure headers such as authorization, www-authenticate, cookie, & cookie2 when redirecting to a untrusted site.
