Version Details and Security Vulnerabilities

📦

rollup-plugin-multi-entry

2.1.0

Comparision Betweeen 2.1.0 and 2.0.2

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

6.43 KB

N/A

Version 2.1.0 Details

Rollup Plugin Multi Entry streamlines the process of using multiple entry points in Rollup projects. Comparing version 2.1.0 with the older 2.0.2 reveals significant updates that benefit developers. The core functionality remains the same – enabling the bundling of numerous entry files into a single output – but the underlying tooling has been modernized.

A key difference lies in the dependency management. Version 2.1.0 updates its dependency matched to ^1.0.2. Version 2.0.2 used ^0.4.4. More importantly, the newer version adopts a more modern build setup, evident in the shift from older Babel presets and plugins like babel-preset-es2015 and babel-plugin-external-helpers to the newer @babel/preset-env and @babel/plugin-transform-flow-strip-types. This transition ensures better compatibility with current JavaScript standards and improved tree shaking for smaller bundle sizes. Also, version 2.1.0 adds a lot of useful dev dependencies that were totally missing in version 2.0.2 like @commitlint/config-conventional, commitlint, globby, husky, lint-staged, prettier, prettier-check.

Developers upgrading should note the potential breaking changes associated with the Babel update. The updated development dependencies indicate a focus on code quality, automated linting, and consistent formatting (Prettier). Consequently, version 2.1.0 uses newer versions of Rollup and related plugins. This package benefits from modern tooling and improves compatibility with recent JavaScript features and Rollup configurations, making it a worthwhile upgrade for those seeking enhanced build processes and code maintainability.

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.