Version Details and Security Vulnerabilities

📦

eslint-config-prettier

6.8.0

Comparision Betweeen 6.8.0 and 6.7.0

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

58.26 KB

57.97 KB

Version 6.8.0 Details

Eslint-config-prettier version 6.8.0 brings a subtle yet important set of updates compared to version 6.7.0, impacting developers seeking seamless integration between ESLint and Prettier for code formatting. The core benefit remains the same: eliminating ESLint rules that conflict with Prettier, ensuring a smooth and consistent formatting workflow.

A key change lies in the updated development dependencies. Notably, TypeScript is bumped from version 3.7.2 to 3.7.4, potentially addressing bug fixes or performance improvements within the TypeScript compilation process. Furthermore, several ESLint plugin versions receive updates: eslint-plugin-react advances from 7.16.0 to 7.17.0, eslint-plugin-unicorn jumps from 13.0.0 to 15.0.1, eslint-plugin-flowtype from 4.4.1 to 4.5.2, eslint-plugin-prettier from 3.1.1 to 3.1.2, and @typescript-eslint/parser and @typescript-eslint/eslint-plugin both move from 2.8.0 to 2.13.0. These upgrades likely include bug fixes, new features, and enhanced compatibility with the latest ESLint and language features. The updated eslint-plugin-unicorn version is particularly significant, potentially bringing many new and useful rules that help enforce code quality and stylistic consistency.

Developers relying on these specific plugins should evaluate the changes in their respective changelogs to understand the full impact of these updates on their projects. The increase in unpacked size from 59360 to 59662 suggests the inclusion of new rules or expanded configurations, indicating that version 6.8.0 offers a more comprehensive set of configurations. The release date also confirms that this is a relatively fresh update, incorporating recent improvements and fixes.

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.