Version Details and Security Vulnerabilities

📦

mini-css-extract-plugin

2.2.0

Comparision Betweeen 2.2.0 and 2.1.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

79.29 KB

77.94 KB

Version 2.2.0 Details

Mini-css-extract-plugin streamlines CSS management within webpack projects, extracting styles into separate .css files for improved performance and cacheability. Comparing versions 2.2.0 and 2.1.0 reveals subtle, but impactful changes relevant to developers.

A key difference lies in the dependencies. Version 2.2.0 updates schema-utils from ^3.0.0 to ^3.1.0, and devDependencies such as husky, eslint, @commitlint/cli has been upgraded to newer versions, which is something to be concerned if your existing project has any compatibility issues. These updates likely incorporate bug fixes, performance improvements, and new features within those underlying utilities.

Notably, the core functionality and peer dependency on webpack version 5 remain consistent between versions, ensuring continued compatibility with existing webpack 5 projects that use this plugin. Both versions maintain the MIT license, author and funding details. Also dist details such as the fileCount stays at 11, unpacked size is relatively unchanged from 79807 to 81194.

For developers, these updates suggest a focus on stability and security. While the core extraction functionality persists, keeping abreast of dependency updates is crucial. While the overall impact of these versions might not be large, it is important to run full integration suite to verify that the upgrades don't introduce any bugs in your software. Checking latest github release would be a helpful read.

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.