Version Details and Security Vulnerabilities

📦

html-webpack-tags-plugin

3.0.0

Comparision Betweeen 3.0.0 and 2.0.17

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

72.05 KB

71.22 KB

Version 3.0.0 Details

The html-webpack-tags-plugin saw a significant update moving from version 2.0.17 to 3.0.0. Both versions enable developers to inject custom HTML tags into their HTML files during the webpack build process, offering a flexible way to manage assets and meta-information. Core dependencies like glob, minimatch, and slash remain relatively consistent, indicating stability in the fundamental file matching and path handling capabilities.

The notable changes primarily reside in thedevDependencies, reflecting updates in the supported ecosystem of tools. Version 3.0.0 embraces newer versions of key webpack-related packages, including html-webpack-plugin (v5.0.0), webpack (v5.20.1), css-loader (v5.0.1), and mini-css-extract-plugin (v1.3.5) which provide better support for modern JavaScript and CSS features. Consequently, developers using newer webpack versions will benefit from the updated compatibility and performance improvements in version 3.0.0. Version 2.0.17 relies on older html-webpack-plugin (v3.2.0 and v4.0.0-beta.8) and webpack (v4.40.2). The upgrade to cheerio (^1.0.0-rc.5 vs ^1.0.0-rc.3) and puppeteer (^7.0.0 vs 1.20.0) hints at improvements to the plugin's testing and HTML manipulation capabilities too. Finally, the jump in semistandard version implies adherence to more recent code style guidelines, potentially improving code quality. Developers should consider these dependency updates to ensure compatibility with their existing webpack configuration.

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.