@storybook/addon-viewport is a valuable tool for developers using Storybook to build responsive components and design systems. It simplifies testing and visualizing components across different screen sizes and orientations directly within the Storybook environment. The addon allows developers to define and switch between various viewport configurations, mimicking different devices and resolutions, ensuring a consistent and adaptable user experience.
Between versions 6.1.12 and 6.1.14, while the core functionality remains consistent, there are key differences to note. Both versions share the same set of dependencies, including essentials like global, core-js, prop-types, memoizerific, and other core Storybook packages (@storybook/api, @storybook/addons, @storybook/theming, @storybook/components, @storybook/core-events, @storybook/client-logger). The peer dependencies, requiring react and react-dom versions ^16.8.0 || ^17.0.0, are also identical, indicating compatibility with a wide range of React projects.
The primary distinction lies in the updated versions of the internal Storybook packages. Version 6.1.14 upgrades these dependencies (e.g., @storybook/api, @storybook/addons) from 6.1.12 to 6.1.14, suggesting bug fixes, performance improvements, or minor feature enhancements within the Storybook ecosystem itself. The update does not reflect drastic changes on the addon's interface or usage, therefore upgrading primarily brings improvements on performance or compatibility of the inner packages. For developers, upgrading from 6.1.12 to 6.1.14 ensures access to the latest refinements and stability improvements within the broader Storybook environment, making it a worthwhile update for those seeking the most up-to-date Storybook experience. The file count and unpacked size are the same between versions.
All the vulnerabilities related to the version 6.1.14 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.