Version Details and Security Vulnerabilities

📦

eslint-plugin-standard

1.2.0

Comparision Betweeen 1.2.0 and 1.1.0

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

N/A

Unpacked Size

N/A

Version 1.2.0 Details

Eslint-plugin-standard offers ESLint rules mirroring the popular Standard code style, ensuring code consistency across JavaScript projects. Comparing version 1.2.0 with its predecessor, 1.1.0, reveals key updates relevant to developers. Both versions maintain the same core functionality: enforcing Standard's linting rules through ESLint. They share dependencies like requireindex for rule organization. Also both versions lists Jamund Ferguson as author.

The crucial difference lies in the supported ESLint version. Version 1.1.0 relies on ESLint 0.24.1 as a development dependency. Version 1.2.0 updates that dependency to ESLint ^1.0.0. This signifies a move to support a newer major version of ESLint, likely incorporating bug fixes, performance enhancements, and potentially new features introduced in ESLint 1.x. The peer dependency definition also reflects and reinforces this required ESLint version.

Developers using eslint-plugin-standard should pay close attention to the ESLint version compatibility. Upgrading to version 1.2.0 necessitates upgrading to ESLint 1.x. This could involve adjustments to their ESLint configuration as breaking changes may have occurred between ESLint 0.24.1 and 1.0.0. If a project is locked to an older ESLint version, sticking with eslint-plugin-standard 1.1.0 might be necessary. Ultimately, aligning dependencies ensures smooth integration and avoids potential conflicts during the linting process. Version 1.2.0 was released on August 3rd, 2015, approximately 10 days after version 1.1.0.

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.