Version Details and Security Vulnerabilities

📦

eslint-plugin-standard

4.1.0

Comparision Betweeen 4.1.0 and 4.0.2

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

28.03 KB

27.7 KB

Version 4.1.0 Details

Eslint-plugin-standard, a popular ESLint plugin designed to enforce the widely adopted Standard code style, saw a release of version 4.1.0 following version 4.0.2. Both versions maintain consistent core functionality, acting as an intermediary or bridge to integrate the Standard linter directly into ESLint workflows. Developers leveraging earlier versions of eslint-plugin-standard will find the upgrade path smooth.

While the core features and developer dependencies such as eslint, mocha, and standard remain practically unchanged, the most notable difference lies in the unpacked size of the package. Version 4.1.0 has a slightly larger footprint at 28707 bytes compared to version 4.0.2's 28365 bytes. This increase could stem from minor updates in the core rules, documentation enhancements, or adjustments to internal tooling. This difference is usually negligible for most use cases. The release dates, October 22nd, 2020 for version 4.0.2 and November 10th, 2020 for version 4.1.0, indicate a relatively short interval between releases suggesting the newer version incorporates bug fixes, performance improvements, or minor rule adjustments identified shortly after the previous release. Developers should review the changelog on the project's GitHub repository to get more specific details. Both versions are licensed under the MIT license, with funding options available through GitHub Sponsors and Patreon, ensuring the project's sustainability and continued development. The peer dependency on ESLint (>=5.0.0) remains consistent, indicating the plugin's continued compatibility with a broad range of ESLint versions.

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.