Version Details and Security Vulnerabilities

📦

rollup-plugin-npm

1.0.0

Comparision Betweeen 1.0.0 and 0.1.0

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

N/A

Unpacked Size

N/A

Version 1.0.0 Details

Rollup-plugin-npm, a tool designed to bundle third-party dependencies residing in node_modules for efficient JavaScript module bundling with Rollup, saw a significant update moving from version 0.1.0 to 1.0.0. While both versions share the core functionality and the same dependency on "builtin-modules," several key differences emerge in their development dependencies, impacting the developer workflow and potentially the supported features.

The most notable change is the introduction of rollup-plugin-babel at version ^1.0.0 in version 1.0.0, while rollup-plugin-npm version 0.1.0 used gobble-rollup-babel at version ^0.6.1 for the same functionality. This indicates a shift in how Babel transformations are handled within the Rollup bundling process. Developers upgrading should investigate the implications of this change, ensuring their Babel configurations are compatible with rollup-plugin-babel.

Furthermore, the rollup package itself was upgraded from version 0.19.2 to 0.20.0. This is important because it signifies that developers using the newer version of rollup-plugin-npm are using newer functionality exposed by rollup, which may include perfomance enhancements or solve edge cases.

These modifications suggest potential improvements in build performance, compatibility with modern JavaScript syntax, and enhanced debugging capabilities. Also developers using rollup version 0.19.2 can not directly upgrade to the new version of the npm plugin and will need to upgrade rollup first. Released just a few days apart in October 2015, these versions mark a moment of rapid evolution in the Rollup ecosystem, providing developers with increasingly sophisticated tools for managing JavaScript 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.