Version Details and Security Vulnerabilities

📦

eslint-config-prettier

6.11.0

Comparision Betweeen 6.11.0 and 6.10.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

60.07 KB

59.77 KB

Version 6.11.0 Details

eslint-config-prettier version 6.11.0 introduces several updates and improvements compared to version 6.10.1, particularly in its development dependencies. Developers will find the updated versions of these dependencies crucial for enhanced compatibility and a smoother development experience. Notably, prettier is upgraded from 2.0.1 to 2.0.5, ensuring that the tool aligns with the latest formatting standards and incorporates recent improvements. Similarly, @typescript-eslint/parser and @typescript-eslint/eslint-plugin jump from version 2.24.0 to 2.29.0, bringing in updated TypeScript parsing and linting capabilities, bug fixes and potential performance enhancements. The eslint-plugin-prettier also sees an upgrade from 3.1.2 to 3.1.3. While seemingly minor, this update likely includes important bug corrections or compatibility adjustments. Other relevant updates include cross-spawn updating from 7.0.1 to 7.0.2 and eslint-plugin-unicorn updating from 17.2.0 to 18.0.1, potentially providing additional features and fixes. Developers can leverage these changes for better code quality and consistency when integrating Prettier with ESLint in their projects to ensure a more streamlined and effective workflow. These dependency updates are particularly useful for developers working with TypeScript/JavaScript projects utilizing Prettier, ESLint, and related plugins, providing access to the newest features and fixes from these tools.

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.