Version Details and Security Vulnerabilities

📦

@storybook/addons

6.1.18

Comparision Betweeen 6.1.18 and 6.1.17

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

55.61 KB

Version 6.1.18 Details

@storybook/addons version 6.1.18 represents a minor update over its predecessor, 6.1.17, both serving as the central hub for Storybook addons. These addons extend Storybook's functionality, offering developers tools for enhanced UI testing, documentation, accessibility checks, and more. The core functionality remains consistent between the two versions, providing a unified store for managing and interacting with these addons.

A key aspect for developers is the consistent dependency structure. Both versions rely on a suite of core Storybook packages such as @storybook/api, @storybook/router, @storybook/theming, @storybook/channels, @storybook/core-events and @storybook/client-logger, all aligned to their respective version numbers (6.1.18 and 6.1.17 respectively), ensuring compatibility and a cohesive Storybook ecosystem. They also include 'global', 'core-js', and 'regenerator-runtime' to provide necessary polyfills and runtime support.

Crucially, both versions maintain the same peer dependency requirements for React and React DOM, requiring versions ^16.8.0 or ^17.0.0. This indicates no breaking changes regarding React compatibility between these releases. The distribution details show identical file counts and unpacked sizes suggesting that the code changes between the versions are minimal. The primary difference lies in the release date, with version 6.1.18 being released approximately ten days after 6.1.17. This suggests that 6.1.18 likely includes bug fixes, internal improvements, or minor feature enhancements that, while not fundamentally altering the addon system, contribute to a more polished and reliable developer experience. Developers should consider upgrading to 6.1.18 to benefit from these incremental improvements.

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.