Version Details and Security Vulnerabilities

📦

eslint

7.5.0

Comparision Betweeen 7.5.0 and 7.4.0

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

403

402

Unpacked Size

3 MB

2.97 MB

Version 7.5.0 Details

ESLint version 7.5.0 introduces several dependency updates and enhancements compared to version 7.4.0, impacting developers who rely on this popular JavaScript linting tool. A notable change is the update to espree from version 7.1.0 to 7.2.0, potentially bringing parser improvements and support for newer JavaScript syntax. Additionally, eslint-utils advances from version 2.0.0 to 2.1.0, offering potentially improved utility functions for rule development. The dependency eslint-visitor-keys is also bumped from 1.2.0 to 1.3.0 which usually reflects updates to the AST traversal, an important internal part of the linter.

In the development dependencies, a significant update is puppeteer upgrading from v2.1.1 to v4.0.0, this is relevant if you are using ESLint for browser environment tests. Furthermore, while most development dependencies remain consistent, small changes in versions of @babel/core, eslint-plugin-eslint-plugin, are observed. A key difference is that 7.5.0 has 403 files compared to 402 in 7.4.0. It's also worth noticing is the unpacked size of the package grew to 3145462 bytes from 3117857, this could mean larger runtime and more disk space required.

Developers should consider these updates when upgrading, especially those who have custom rules that utilize the previously mentioned dependencies. Reviewing the changelogs for espree, eslint-utils and eslint-visitor-keys and puppeteer is recommended to understand the specific changes and ensure compatibility with existing ESLint configurations. The newer version will likely bring with it better support for the newest Javascript/ECMAScript standards.

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.