Version Details and Security Vulnerabilities

📦

parcel

2.9.1

Comparision Betweeen 2.9.1 and 2.9.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

38.54 KB

Version 2.9.1 Details

Parcel, the zero-configuration web application bundler, saw a minor version update from 2.9.0 to 2.9.1, released just a day apart. Both versions promise a blazing fast bundling experience, making web development easier and more efficient. The core functionality remains identical, with no breaking changes or new features introduced between these minor releases.

The primary difference lies in the updated versions of Parcel's internal dependencies. Core packages like @parcel/fs, @parcel/core, @parcel/utils, @parcel/events, @parcel/logger, @parcel/diagnostic, @parcel/reporter-cli, @parcel/config-default, @parcel/package-manager, @parcel/reporter-tracer, and @parcel/reporter-dev-server all see a version bump from 2.9.0 to 2.9.1. These internal updates typically incorporate bug fixes, performance improvements, and minor adjustments to the underlying architecture.

For developers using Parcel, upgrading from 2.9.0 to 2.9.1 is a recommended step to ensure you're leveraging the latest refinements and stability enhancements. While the changes might not be immediately apparent, these internal updates contribute to a more robust and reliable bundling process. The devDependencies, @babel/core and @parcel/babel-register remain consistent across both versions. The file count and unpacked size of the distribution are also the same. Developers can expect a seamless transition with this minor update, enjoying the continued benefits of Parcel's ease of use and speed.

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.