Version Details and Security Vulnerabilities

📦

eslint-config-prettier

4.2.0

Comparision Betweeen 4.2.0 and 4.1.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

49.38 KB

49.03 KB

Version 4.2.0 Details

Eslint-config-prettier version 4.2.0 introduces several updates and improvements compared to its predecessor, version 4.1.0. Both versions aim to disable ESLint rules that conflict with Prettier, ensuring a smooth formatting experience. A key difference lies in the updated development dependencies. Version 4.2.0 bumps the core ESLint version from 5.14.1 to 5.16.0, and Typescript version is moved from 3.3.3333 to 3.4.5.

Notably, eslint-plugin-unicorn sees a significant upgrade from version 7.1.0 to 8.0.2. Additionally, @typescript-eslint/parser and @typescript-eslint/eslint-plugin are updated from version 1.4.2 to 1.7.0. These updates bring the latest linting rules and parser enhancements to your projects, offering finer-grained control over code style and potential error detection. The update in dependencies provides enhanced code analysis and compatibility with the latest language features.

Prettier remains at version 1.17.0 after the update from 1.16.4, ensuring consistent code formatting capabilities. The release dates indicate that version 4.2.0 (April 25, 2019) follows version 4.1.0 (February 26, 2019), reflecting ongoing efforts to refine the integration between ESLint and Prettier. Developers should consider upgrading to version 4.2.0 to leverage the latest bug fixes, performance improvements, and enhanced compatibility with other popular tools in the ecosystem, thus promoting cleaner and more maintainable codebases.

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.