Version Details and Security Vulnerabilities

📦

@rollup/plugin-commonjs

25.0.7

Comparision Betweeen 25.0.7 and 25.0.6

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

179.01 KB

Version 25.0.7 Details

@rollup/plugin-commonjs offers crucial functionality for developers using Rollup, converting CommonJS modules into the modern ES2015 format, enabling seamless integration of legacy code within contemporary JavaScript projects. The latest version, 25.0.7, includes a subtle but important update: a bump in the magic-string dependency, moving from version 0.27.0 to version 0.30.3. While seemingly minor, this change addresses potential under-the-hood bug fixes and performance improvements within magic-string, which directly impacts the plugin's source code transformation capabilities. Developers should see improved accuracy and potentially faster build times when dealing with complex CommonJS modules.

Both versions maintain the same core dependencies like glob for file matching, commondir for path manipulation, is-reference for accurate identifier analysis, and @rollup/pluginutils for Rollup plugin utilities, suggesting that the fundamental approach to CommonJS conversion remains consistent. The peer dependency on Rollup remains flexible, supporting versions 2.68.0, 3.x, and 4.x, allowing developers to integrate the plugin regardless of their Rollup version. Also, the libraries used for testing and development are the same between the two versions: shx, rollup, source-map, typescript, locate-character, require-relative, source-map-support, @rollup/plugin-json and @rollup/plugin-node-resolve. Reviewing magic-string's changelog between these versions would provide even greater insight into the specific fixes and enhancements included in version 25.0.7, so you can understand if some bug that was affecting you was fixed.

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.