Version Details and Security Vulnerabilities

📦

@storybook/theming

6.5.0

Comparision Betweeen 6.5.0 and 6.4.22

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

1.47 MB

116.3 KB

Version 6.5.0 Details

Version 6.5.0 of @storybook/theming brings significant updates compared to its predecessor, v6.4.22, impacting developers building custom themes and UI components within Storybook. Notably, the dependency structure has undergone a considerable overhaul. The older version relies on @emotion/core, @emotion/styled (v10), and emotion-theming, while v6.5.0 migrates to @emotion/cache, @emotion/react, and the latest @emotion/styled (v11), aligning with modern Emotion practices and performance improvements. This upgrade likely unlocks access to newer Emotion features, improved CSS-in-JS performance, and better compatibility with recent React versions.

Furthermore, regenerator-runtime has been added as a direct dependency in v6.5.0, possibly to ensure broader browser compatibility for asynchronous operations within the theming components. The developer dependencies also see adjustments, including updates to polished, ts-dedent and @types/node. While the peer dependencies remain largely consistent, supporting React versions 16.8.0 through 18.0.0, the internal changes suggest a modernized codebase.

Developers upgrading should be aware of potential breaking changes related to the Emotion migration, specifically if they have deeply customized themes using older APIs. The unpacked size of v6.5.0 is significantly larger than v6.4.22, indicating a richer feature set or potentially larger bundled assets, something to consider for performance-sensitive environments.

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.