Version Details and Security Vulnerabilities

📦

parcel

2.15.2

Comparision Betweeen 2.15.2 and 2.15.1

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

42.85 KB

Version 2.15.2 Details

Parcel, the zero-configuration web application bundler, released version 2.15.2, a minor update following closely on the heels of version 2.15.1. Both versions maintain the core promise of blazing-fast performance and ease of use, appealing to developers seeking streamlined workflows. Primarily, the changes appear to be internal, focusing on updates and refinements within Parcel's core packages. Developers will notice that many of Parcel's internal dependencies, such as @parcel/fs, @parcel/core, @parcel/utils, @parcel/events, @parcel/logger, @parcel/diagnostic, @parcel/reporter-cli, @parcel/feature-flags, @parcel/config-default, @parcel/package-manager, @parcel/reporter-tracer, and @parcel/reporter-dev-server have all been bumped from version 2.15.1 to 2.15.2. This suggests that the update primarily contains bug fixes, performance improvements, or minor feature enhancements within these specific modules. The core dependencies like chalk, get-port, commander, and @babel/core remain at the same versions, indicating no major breaking changes or feature additions concerning these widely used tools. Given the rapid release sequence, developers are advised to review the detailed changelog (available on the Parcel GitHub repository) for comprehensive insight into the specific changes implemented in version 2.15.2. Developers looking for stability or who have customized internal parcel configurations should review changes closely to ensure no unexpected impact to their workflows.

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.