Version Details and Security Vulnerabilities

📦

eslint-config-next

13.1.0

Comparision Betweeen 13.1.0 and 13.0.7

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.54 KB

Version 13.1.0 Details

The eslint-config-next package provides a pre-configured ESLint setup tailored for Next.js applications, streamlining the process of enforcing consistent code style and identifying potential issues. Comparing versions 13.1.0 and 13.0.7, developers will find mainly internal updates related to the core Next.js ESLint plugin. Both versions share identical dependencies on essential ESLint plugins like eslint-plugin-react, eslint-plugin-import, and eslint-plugin-jsx-a11y, ensuring robust support for React, import/export conventions, and accessibility best practices. They also leverage @typescript-eslint/parser for effective TypeScript linting and eslint-plugin-react-hooks for enforcing React Hooks rules.

A key dependency, @next/eslint-plugin-next, sees a direct version bump matching the parent eslint-config-next version, reflecting internal improvements and rule adjustments specific to Next.js projects. The peer dependencies, eslint and typescript, remain consistent, indicating that both versions are compatible with the same range of ESLint and TypeScript versions. This ensures a seamless upgrade experience without requiring major updates to your core tooling. Developers upgrading from 13.0.7 to 13.1.0 can expect refinements within the Next.js specific linting rules, potentially catching more nuanced issues related to Next.js features and best practices. The upgrade promises a more aligned linting experience with the latest Next.js idioms.

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.