Version Details and Security Vulnerabilities

📦

webpack-manifest-plugin

1.2.0

Comparision Betweeen 1.2.0 and 1.1.2

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

N/A

Unpacked Size

N/A

Version 1.2.0 Details

Webpack Manifest Plugin version 1.2.0 introduces several notable changes compared to its predecessor, version 1.1.2. Both versions serve the core purpose of generating asset manifests for Webpack projects, aiding in efficient asset management within applications. The fundamental dependencies on lodash (>=3.5 <5) and fs-extra (^0.30.0) remain consistent, ensuring continued compatibility and functionality related to file system operations and utility functions.

The most significant divergence lies in the development dependencies. Version 1.2.0 adds nyc (^10.3.2) and codecov (^2.2.0), indicating an increased focus on code coverage and quality assurance. This suggests a commitment to improved testing and reliability. Additionally, rimraf (^2.6.1) is included, a utility for recursively deleting directories, potentially used for cleanup tasks during development or testing. Another key difference is the peer dependency requirements for webpack meaning that version 1.2.0 declares compatibility with Webpack versions 1, 2, and 3.

For developers choosing between these versions, opting for 1.2.0 is generally recommended. The inclusion of code coverage tools points towards enhanced stability and a more robust testing environment. While the core functionality remains the same, the added development dependencies make version 1.2.0 the preferred choice for projects prioritizing code quality and maintainability, especially if using a webpack version greater than 1.

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.