@storybook/addon-viewport is a valuable tool for Storybook users, enabling developers to build and test responsive components effectively by simulating different screen sizes and orientations directly within the Storybook environment. Examining versions 6.1.15 and 6.1.14, the core functionality remains consistent, focusing on providing a seamless way to visualize how components adapt across various devices. The description highlights the addon's purpose: "Build responsive components by adjusting Storybook’s viewport size and orientation," which emphasizes its utility for responsive design workflows.
The key difference lies in the updated versions of the internal @storybook packages. Version 6.1.15 depends on "@storybook/api":"6.1.15","@storybook/addons":"6.1.15","@storybook/theming":"6.1.15","@storybook/components":"6.1.15","@storybook/core-events":"6.1.15","@storybook/client-logger":"6.1.15" while the version 6.1.14 depends on "@storybook/api":"6.1.14","@storybook/addons":"6.1.14","@storybook/theming":"6.1.14","@storybook/components":"6.1.14","@storybook/core-events":"6.1.14","@storybook/client-logger":"6.1.14". This suggests that version 6.1.15 incorporates bug fixes, performance enhancements, or new features within the Storybook ecosystem itself, rather than a significant overhaul of the viewport addon's core functionality. For developers, upgrading to 6.1.15 is recommended to benefit from the latest improvements and ensure compatibility with other Storybook addons and core components. The peer dependencies on React and React-DOM remain the same, indicating no breaking changes related to the underlying UI framework. Both versions maintain identical file counts and unpacked sizes, further supporting the idea of incremental updates rather than substantial alterations.
All the vulnerabilities related to the version 6.1.15 of the package
Cross site scripting in markdown-to-jsx
Versions of the package markdown-to-jsx before 7.4.0 are vulnerable to Cross-site Scripting (XSS) via the src property due to improper input sanitization. An attacker can execute arbitrary code by injecting a malicious iframe element in the markdown.