Version Details and Security Vulnerabilities

📦

lint-staged

16.1.1

Comparision Betweeen 16.1.1 and 16.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

132.67 KB

129.55 KB

Version 16.1.1 Details

Lint-staged version 16.1.1 introduces subtle but potentially impactful updates compared to version 16.1.0, primarily affecting the development environment. While the core functionality of linting staged files via Git remains consistent, developers should note the updated dependencies. Notably, the jest testing framework jumps from version 29.7.0 to 30.0.0, representing a major version upgrade. This likely includes new features, bug fixes, and possibly breaking changes that developers should investigate before upgrading.

Furthermore, eslint receives an upgrade from 9.27.0 to 9.29.0 alongside with @eslint/js which also moves from 9.27.0 to 9.29.0. Moreover, eslint-plugin-n advances from 17.18.0 to 17.20.0, eslint-plugin-jest moves significantly from 28.11.0 to 28.13.5 and eslint-plugin-prettier goes from 5.4.0 to 5.4.1. These updates suggest improvements in linting rules, performance, or compatibility with newer JavaScript features. The typescript version remains the same at 5.8.3. These updates might influence the existing linting configuration and may require adjustments to the project's ESLint configuration to ensure smooth integration and desired linting behavior.

These updated development dependencies may introduce new features, improved performance, or breaking changes within the linting and testing processes, so it is important to read the dependecies changelogs before upgrading. The filesize also suffered a small increase, and for sure this new version includes some fix/improvements.

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.