Version Details and Security Vulnerabilities

📦

eslint-config-next

14.2.13

Comparision Betweeen 14.2.13 and 14.2.12

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

Version 14.2.13 Details

eslint-config-next has released a new version, 14.2.13, following closely on the heels of version 14.2.12. Both configurations provide the standard ESLint setup optimized for Next.js projects, ensuring code quality and consistency. The core functionalities and dependencies remain largely the same, meaning the update is likely a minor one containing bug fixes or small enhancements. Key dependencies for code linting haven't changed: eslint-plugin-react, eslint-plugin-import, eslint-plugin-jsx-a11y, @rushstack/eslint-patch, @typescript-eslint/parser, eslint-plugin-react-hooks, eslint-import-resolver-node, @typescript-eslint/eslint-plugin, and eslint-import-resolver-typescript. Of note to developers, the primary difference lies in the version of the core Next.js ESLint plugin dependency, "@next/eslint-plugin-next" which has been bumped from 14.2.12 to 14.2.13 to ensure compatibility and the linter incorporates the latest Next.js best practices and rules. Developers should update primarily for staying current with Next.js specific linting rules. Peer dependencies like ESLint and TypeScript remain compatible with the same versions, minimizing potential breaking changes. While the unpacked size and file count are identical, update to 14.2.13 for the latest recommended linting rules within your Next.js applications. The date shown indicates that this version was released very recently and upgrading guarantees you're using the latest bug fixes.

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.