Version Details and Security Vulnerabilities

📦

webpack-cli

4.7.2

Comparision Betweeen 4.7.2 and 4.7.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

100.04 KB

Version 4.7.2 Details

Webpack CLI version 4.7.2 represents a minor update over the previous stable version, 4.7.1, primarily focusing on dependency upgrades. Both versions serve as command-line interfaces for Webpack, a popular JavaScript bundler, streamlining the development workflow for modern web applications. Developers leverage Webpack CLI to execute Webpack configurations, manage builds, and utilize development servers.

The core functionalities remain consistent between the two versions. Both rely on a suite of dependencies essential for their operation, including execa for executing commands, rechoir for configuration file support, colorette for terminal styling, commander for command-line argument parsing, interpret for handling various file types, import-local for prioritizing local installations, webpack-merge for merging Webpack configurations, and v8-compile-cache for performance optimization. Crucially, both also maintain peer dependency on Webpack versions 4 and 5, ensuring compatibility with a broad range of projects.

The key difference lies in the updated @webpack-cli/serve dependency. Version 4.7.2 upgrades this dependency to version 1.5.1 from 1.5.0 in the prior release. While seemingly minor, such updates often incorporate bug fixes, performance improvements, and potentially, new features related to the development server. Developers utilizing the serve functionality should carefully consider this update, as it may improve their local development experience and fix potential issues. Furthermore, version 4.7.2 was released on 2021-06-07T16:38:45.716Z while version 4.7.1 was released on 2021-06-07T13:07:20.073Z. Both versions remains licensed under the MIT license, ensuring its free use and modification.

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.