Version Details and Security Vulnerabilities

📦

eslint-plugin-prettier

2.6.2

Comparision Betweeen 2.6.2 and 2.6.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

30.21 KB

29.1 KB

Version 2.6.2 Details

Eslint-plugin-prettier version 2.6.2 represents a minor update over the previous stable version 2.6.1, offering developers a refined experience in integrating Prettier's code formatting capabilities directly into their ESLint workflow. Both versions share the core functionality of running Prettier as an ESLint rule, ensuring consistent code style across projects. Key dependencies like "fast-diff" for efficient change detection and "jest-docblock" for handling Jest-style docblocks, remain consistent, maintaining the plugin's core functionality. Development dependencies also remain the same, including tools for testing (mocha), linting (eslint, eslint-plugin-node, eslint-plugin-self, eslint-plugin-eslint-plugin), and configuration (eslint-config-prettier, eslint-config-not-an-aardvark). Prettier itself appears as a development dependency at version 1.10.2. Similarly, peer dependencies require Prettier version 0.11.0 or greater.

The crucial difference between the versions lies in the internal improvements and bug fixes reflected in the "dist" object. While both tarballs contain 5 files, version 2.6.2 has a slightly larger unpacked size of 30935 compared to 2.6.1's 29794, suggesting code refinement within rules, core logic, or documentation. Version 2.6.2 was released on July 6, 2018, implying about two weeks of development to address potential issues found in 2.6.1 which was released on June 23, 2018. Developers should upgrade to 2.6.2 for the latest enhancements and bug fixes, ensuring optimal performance and code formatting precision within their ESLint-driven projects. The MIT license continues to apply, and the source code is hosted on GitHub, encouraging community contributions and transparency.

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.