The eslint-config-next package provides a pre-configured ESLint setup tailored for Next.js projects, streamlining code linting and ensuring best practices. Comparing versions 15.4.0 and 15.4.1, the core functionalities remain consistent, focusing on robust linting for React, import statements, and accessibility through dependencies like eslint-plugin-react, eslint-plugin-import, and eslint-plugin-jsx-a11y. Both versions also include @rushstack/eslint-patch for enhanced ESLint compatibility and utilize @next/eslint-plugin-next which aligns the linter rules with Next.js-specific conventions.
Crucially, both depend on @typescript-eslint/parser and @typescript-eslint/eslint-plugin, allowing seamless integration with TypeScript projects with support for a wide range of typescript versions. eslint-plugin-react-hooks helps enforce React Hooks rules. The eslint-import-resolver-node and eslint-import-resolver-typescript packages ensure that import statements are correctly resolved, enhancing the accuracy of the linting process. The peer dependencies specify that both configurations are compatible with ESLint versions 7.23.0, 8.0.0, and 9.0.0 as well as Typescript versions greater than or equal to 3.3.1.
The most significant difference lies in the version of the @next/eslint-plugin-next dependency; 15.4.0 uses version 15.4.0 and version 15.4.1 correspondingly uses version 15.4.1. Therefore, upgrading provides access to the latest linting rules and improvements specifically designed for Next.js 15.4.1. Choosing the newer version will ensure you are leveraging best practices and up-to-date checks relevant to the latest minor release of Next.js. Both versions were released yesterday.
The are not vulnerabilities for the version 15.4.1 of the package eslint-config-next