Version Details and Security Vulnerabilities

📦

eslint-rule-composer

0.2.0

Comparision Betweeen 0.2.0 and 0.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

15.34 KB

13.57 KB

Version 0.2.0 Details

Eslint-rule-composer is a utility designed to simplify the creation of custom ESLint rules by enabling composition from existing rules. Version 0.2.0 builds upon the foundation established in version 0.1.1, offering developers an enhanced experience in crafting and maintaining complex linting logic. Both versions share the same core development dependencies, including tools for testing (Chai, Mocha), linting (ESLint, eslint-config-airbnb-base, eslint-plugin-import, eslint-plugin-node), and release management, ensuring a consistent development environment.

The key difference between the two versions lies in the internal improvements and potentially bug fixes, reflected in the increased unpacked size of version 0.2.0 (15710 bytes) compared to version 0.1.1 (13897 bytes). This increment, alongside the month-long gap between releases (March 14, 2018 for 0.1.1 and April 14, 2018 for 0.2.0), suggests refinements to the composition logic or added features designed to improve rule building or maintenance. While the absence of detailed changelogs limits precise understanding of edits, the version bump from 0.1.1 to 0.2.0 indicates significant alterations rather than trivial adjustments.

Developers intending to use eslint-rule-composer should prefer version 0.2.0 for its enhanced capabilities. Both versions provide a MIT license and reside in the package's GitHub repository, while Teddy Katz is indicated as the author of both 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.