Version Details and Security Vulnerabilities

📦

eslint-config-next

15.2.2

Comparision Betweeen 15.2.2 and 15.2.1

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

4.79 KB

Version 15.2.2 Details

eslint-config-next versions 15.2.1 and 15.2.2 offer curated ESLint configurations tailored for Next.js projects, ensuring code quality and consistency across development teams. Both versions share a similar foundation, incorporating essential plugins like eslint-plugin-react, eslint-plugin-import, and eslint-plugin-jsx-a11y for React-specific linting, import statement handling, and accessibility best practices, respectively. They also leverage @rushstack/eslint-patch to address ESLint's module resolution quirks.

The primary difference lies in the version of the core Next.js ESLint plugin, @next/eslint-plugin-next. Version 15.2.2 updates this dependency to match its own version number, while 15.2.1 uses the older 15.2.1 version. This update likely incorporates new rules, bug fixes, and improvements specific to Next.js 15.2.2, aligning the linter with the framework's latest features and recommendations.

Importantly, both versions specify peer dependencies for eslint and typescript, indicating compatibility with a range of ESLint (versions 7.23.0, 8.0.0, and 9.0.0) and TypeScript versions (3.3.1 and above). This allows flexibility in choosing the specific ESLint and TypeScript versions that best suit project needs while ensuring compatibility with the configuration. Furthermore, developers will find the setup straightforward, inheriting a sensible default configuration refined by the Next.js team, potentially reducing configuration overhead and promoting cleaner, more maintainable codebases. The consistent file count and unpacked size suggest that the update mainly concentrates on plugin adjustments rather than significant structural alterations. Each release is licensed under MIT.

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.