Version Details and Security Vulnerabilities

📦

rollup

4.43.0

Comparision Betweeen 4.43.0 and 4.42.0

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

2.61 MB

Version 4.43.0 Details

Rollup, a next-generation ES module bundler, has released version 4.43.0, succeeding the previous stable version 4.42.0. Both versions share the same core dependencies like @types/estree, ensuring consistent type definitions. The development dependencies remain largely identical, encompassing tools for testing (nyc, mocha), linting (eslint), code transformation (buble, terser), and UI development (vue, vite). Key dependencies like typescript, eslint, and prettier are held at the same major versions, guaranteeing similar development environments across versions.

A notable difference lies in the optional dependencies. While both versions include fsevents, a file system events monitor, and architecture-specific Rollup binaries (@rollup/rollup-*), the version numbers of these binaries directly correspond to the parent Rollup version. For example, version 4.43.0 utilizes @rollup/rollup-darwin-x64@4.43.0, whereas version 4.42.0 uses @rollup/rollup-darwin-x64@4.42.0. This suggests that these optional dependencies incorporate platform-specific optimizations and bug fixes aligned with their respective Rollup releases.

Developers should consider upgrading to version 4.43.0 to benefit from these potential performance improvements and bug fixes within the platform-specific binaries. The core functionality and development environment remain consistent, minimizing the disruption associated with upgrading. Check the release notes for a comprehensive list of fixes and enhancements provided by the updated architecture-specific packages to make an informed decision. Keep an eye on the releaseDate as well, because that field has an incorrect (future) datestamp in both json blobs and it is not reliable to understand the timing of the releases.

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.