Version Details and Security Vulnerabilities

📦

@storybook/addon-viewport

7.3.2

Comparision Betweeen 7.3.2 and 7.3.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

29.74 KB

Version 7.3.2 Details

@storybook/addon-viewport has been updated from version 7.3.1 to 7.3.2. This addon empowers developers to build and test responsive components directly within the Storybook environment by simulating various viewport sizes and orientations. This eliminates the need for constant manual resizing or device emulators, streamlining the responsive design workflow.

The core functionality remains consistent between the two versions, allowing developers to define and switch between preset viewport configurations, ensuring components render correctly across different devices. Both versions rely on key dependencies such as prop-types, memoizerific, and a suite of core Storybook packages, including @storybook/theming, @storybook/components, @storybook/core-events, @storybook/manager-api, @storybook/preview-api, and @storybook/client-logger for seamless integration within the Storybook ecosystem. The peer dependencies indicate compatibility with React versions 16.8.0 and above, including versions 17 and 18, and corresponding React DOM versions. The licensing remains under the MIT license.

The significant change between version 7.3.1 and 7.3.2 lies within the dependencies using the library internally. Version 7.3.2 includes @storybook/theming, @storybook/components, @storybook/core-events, @storybook/manager-api, @storybook/preview-api, @storybook/client-logger at version "7.3.2" while the previous one had all of them in version "7.3.1". Developers should upgrade to 7.3.2 to maintain compatibility with the rest of their Storybook setup and benefit from any bug fixes, performance improvements, or new features introduced in the core Storybook packages within that incremental update, which is probably related to internal enhancements.

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.