Version Details and Security Vulnerabilities

📦

webpack-cli

4.3.1

Comparision Betweeen 4.3.1 and 4.3.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

211.25 KB

208.49 KB

Version 4.3.1 Details

Webpack-cli version 4.3.1 introduces minor updates and refinements compared to its predecessor, version 4.3.0. Both versions serve as command-line interfaces for webpack, streamlining the build process and offering tools for managing webpack projects. A key difference lies in the dependencies. Version 4.3.1 updates "execa" from version "^4.1.0" to "^5.0.0", potentially bringing performance improvements and bug fixes related to process execution. Further enhancing functionality, "@webpack-cli/info" and "@webpack-cli/serve" have been bumped up from version "1.2.0" to "1.2.1". These internal packages likely include minor feature enhancements or bug resolutions, optimizing the development experience.

Developers using webpack-cli will find that both versions share a robust set of features including configuration file handling, plugin management, and task automation. These versions ensure compatibility with webpack versions 4 and 5 (4.x.x || 5.x.x), providing flexibility for users employing different webpack versions. The core dependencies like "enquirer", "commander", and "webpack-merge" are consistent, solidifying a stable foundation for project building. The updated "execa" is likely a benefit, while the bumps in the internal packages "@webpack-cli/info" and "@webpack-cli/serve" are also a positive signal. Choosing between these versions would depend on precise dependency requirements and recent bug fixes related to process execution.

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.