Version Details and Security Vulnerabilities

📦

rollup-plugin-visualizer

5.3.3

Comparision Betweeen 5.3.3 and 5.3.2

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.9 MB

Version 5.3.3 Details

Rollup Plugin Visualizer, a valuable tool for optimizing your Rollup bundles, has two recently released versions, 5.3.3 and 5.3.2, offering developers insights into bundle composition and size. Both versions share the same core dependencies, including "open," "yargs," "nanoid," and "source-map," ensuring consistent functionality for visualizing bundle contents. The developer dependencies are also identical, featuring tools like "sass," "eslint," "preact," and various Rollup plugins, aimed at enhancing the development and testing process. This consistency in dependencies suggests a minimal or no impact on fundamental features between versions.

The key difference lies in the dist section, specifically the unpackedSize parameter. Version 5.3.3 has an unpacked size of 1995356 bytes, while version 5.3.2 has a size of 1995097 bytes. This small increase of 259 bytes could hint at minor internal adjustments, bug fixes, or insignificant changes to enhance performance. While seemingly small, developers should be aware of potential minimal variations when upgrading. The release dates also indicate a short time span between versions, with version 5.3.3 being published just minutes after version 5.3.2. This rapid release may indicate a quick response to address a minor issue.

For developers already using Rollup Plugin Visualizer, the update from 5.3.2 to 5.3.3 shouldn't introduce major alterations. Keep an eye on the impact that a re-install/update of these files can have on the system that the library is part of. The plugin remains a solid choice for visualizing and analyzing Rollup bundles, thanks to its peer dependency on "rollup" and a comprehensive environment using development dependencies.

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.