Version Details and Security Vulnerabilities

📦

lint-staged

2.0.2

Comparision Betweeen 2.0.2 and 2.0.1

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 2.0.2 Details

Lint-staged is a popular npm package that helps developers ensure code quality by linting files staged for commit in Git. Versions 2.0.1 and 2.0.2 share a common goal: to streamline the linting process. Both versions boast identical dependencies, encompassing crucial tools like ora for visually pleasing spinners, batchflow for managing asynchronous tasks, minimatch for file matching, and npm-which for locating npm package executables. The core functionality remains consistent, leveraging app-root-path, object-assign, and staged-git-files for project root detection, object manipulation, and identifying staged files, respectively. Similarly, their development dependencies match, featuring testing frameworks (mocha, expect), linters (eslint), and build tools (babel-core, babel-preset-*).

The key difference lies in the release date. Version 2.0.2 was published on July 11, 2016, a few days after version 2.0.1, released on July 8, 2016. This suggests that 2.0.2 likely includes bug fixes or minor improvements implemented after the initial 2.0.1 release. While the specific nature of these changes isn't explicitly detailed, developers who prioritize stability and the most up-to-date version should opt for 2.0.2. Both versions are released under the MIT license and maintained in the same GitHub repository. Developers using lint-staged benefit from consistent configuration across these versions utilizing existing setups seamlessly. The author information also remains the same.

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.