Version Details and Security Vulnerabilities

📦

eslint-plugin-prettier

5.2.5

Comparision Betweeen 5.2.5 and 5.2.4

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

32.3 KB

32.27 KB

Version 5.2.5 Details

Eslint-plugin-prettier helps developers maintain consistent code formatting by running Prettier as an ESLint rule. Comparing versions 5.2.5 and 5.2.4, some subtle but important differences exist for developers to consider. Besides the release date, which indicates that version 5.2.5 was released shortly after, the key change lies in the peerDependencies.

Specifically, eslint-config-prettier, a crucial package for disabling ESLint rules that conflict with Prettier, has a more specific version range in 5.2.5. Version 5.2.4 uses a wildcard (*), allowing any version of eslint-config-prettier. However, 5.2.5 pins this dependency down to ">= 7.0.0 <10.0.0 || >=10.1.0". This means version 5.2.5 explicitly supports versions 7, 8, and 9, but excludes version 10.0.0 because some incompatibility with this version might be expected. After 10.0.0 and as stated in the dependency ">=10.1.0" the versions are supported again.

This change is important for developers relying on specific versions of eslint-config-prettier. Developers using version 10.0.0 might want to downgrade to version 8 or upgrade to a newer version. This is made to ensure the compatibility and stability, providing a smoother integration with the specific versions of ESLint and Prettier that eslint-config-prettier supports. By defining a specific version range, version 5.2.5 aims to prevent unexpected formatting issues or errors arising from incompatible configurations.

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.