Version Details and Security Vulnerabilities

📦

eslint-config-prettier

3.2.0

Comparision Betweeen 3.2.0 and 3.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

40.01 KB

35.66 KB

Version 3.2.0 Details

Eslint-config-prettier, a valuable tool for developers seeking seamless integration between ESLint and Prettier, saw an update from version 3.1.0 to 3.2.0. Both versions aim to disable ESLint rules that conflict with Prettier's formatting, ensuring a consistent and clean codebase.

Key updates in version 3.2.0 involve upgrades to several development dependencies. The core linter, ESLint, jumps from version 5.6.0 to 5.9.0, potentially bringing in new linting rules and bug fixes. Prettier itself sees an update from 1.14.3 to 1.15.2, likely including new formatting options and addressing previous formatting inconsistencies. Babel-eslint updates from version 9.0.0 to 10.0.1 which means, better compatibility with latest Javascript features. Flowtype support is updated with eslint-plugin-flowtype, from 2.50.1 to 3.2.0. Eslint-plugin-prettier gets a major upgrade, too, from version 2.6.2 to 3.0.0. This can include new features and performance improvements in how Prettier is integrated into the ESLint workflow. Version 3.2.0 introduces the dev dependency doctoc and removes replace.

For developers, upgrading to 3.2.0 offers enhanced compatibility with newer versions of ESLint, Prettier, Babel and Javascript features. The updated eslint-plugin-prettier is likely to improve the efficiency and accuracy of Prettier integration. The release includes minor file count and unpacked size changes, hinting under-the-hood improvements and optimization. Choosing the right version hinges on your project's dependency requirements and desired level of integration sophistication between ESLint and Prettier.

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.