Version Details and Security Vulnerabilities

📦

webpack-manifest-plugin

3.2.0

Comparision Betweeen 3.2.0 and 3.1.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

21.31 KB

20.76 KB

Version 3.2.0 Details

Webpack Manifest Plugin simplifies asset management in webpack builds, generating a manifest file that maps module filenames to their corresponding output filenames. Version 3.2.0 and 3.1.1 both share the core functionality and dependencies like tapable and webpack-sources, essential for plugin integration within the webpack ecosystem. Key development dependencies such as ava for testing, prettier for code formatting, and webpack itself for development, remain consistent, ensuring a stable development environment.

The subtle but important change lies in the peerDependencies. Version 3.1.1 specifies "webpack": ">=4.44.2", while version 3.2.0 necessitates "webpack": "^4.44.2". The newer version enforces a stricter matching, limiting compatibility to webpack versions strictly within the 4.44.2 range. The older version declared peer dependency allows a higher patch version of webpack 4 to be used. This change in peer dependency may affect projects relying on specific patch versions, requiring developers to update or downgrade their webpack version accordingly when upgrading to version 3.2.0. Both versions are licensed under MIT, ensuring flexibility for developers. Ultimately, the update focuses largely on dependency constraints, so developers should carefully review their existing webpack configuration before upgrading to ensure compatibility.

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.