-
Notifications
You must be signed in to change notification settings - Fork 0
chore(deps-dev): bump the tooling group across 1 directory with 3 updates #85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
dependabot
wants to merge
1
commit into
main
Choose a base branch
from
dependabot/npm_and_yarn/tooling-c85b07e819
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: Sentriscloud/frontend
Length of output: 1669
🌐 Web query:
eslint-config-next 16.2.6 peer dependencies ESLint 10 support💡 Result:
As of May 18, 2026, eslint-config-next version 16.2.6 does not officially support ESLint 10 as a peer dependency [1]. Users attempting to use ESLint 10 with this version of eslint-config-next will encounter peer dependency resolution errors [1]. This is because the package and its underlying dependencies (such as eslint-plugin-import, eslint-plugin-react, and eslint-plugin-jsx-a11y) currently define peer dependency ranges that do not include ESLint 10 [1]. While there has been active tracking of this issue within the Next.js repository (e.g., issue
#91702), official support remains pending as the ecosystem works to update upstream plugin dependencies to be compatible with ESLint 10 [1]. In the interim, users often resolve these installation conflicts by using package manager flags such as --legacy-peer-deps or by using overrides in their package.json to force compatibility [2][3].Citations:
eslintv10ineslint-config-nextvercel/next.js#91702🏁 Script executed:
Repository: Sentriscloud/frontend
Length of output: 346
🌐 Web query:
eslint-config-next ESLint 10 support GitHub issue Next.js May 2026💡 Result:
As of May 18, 2026, official support for ESLint 10 in eslint-config-next remains an active area of development and is not yet fully resolved [1][2]. While ESLint 10 has been released and is currently at version 10.3.0 [3], users attempting to use it with eslint-config-next have encountered peer dependency conflicts and runtime errors [1][4]. Specifically, the underlying plugins included in the Next.js configuration—such as eslint-plugin-react—have faced compatibility issues with ESLint 10, often manifesting as TypeError: contextOrFilename.getFilename is not a function [1][4]. Key points regarding the current status: - Development Tracking: The issue is being tracked in the Next.js repository (notably issue
#89764) [1][2]. Efforts to resolve this involve both updating the Next.js configuration and waiting for upstream dependencies (like eslint-plugin-react) to officially support ESLint 10 [1][4]. - Workarounds: Some developers have attempted to use compatibility layers or manual overrides to bypass these peer dependency constraints, but these are not official solutions [2]. - Upstream Dependencies: The primary blocker is that several core ESLint plugins used by Next.js have not yet fully updated their peer dependency ranges or internal logic to accommodate the breaking changes introduced in ESLint 10 [1][4]. Users are advised to monitor the official Next.js GitHub repository for updates on this integration [1][5].Citations:
eslintv10ineslint-config-nextvercel/next.js#91702Critical: ESLint 10 incompatible with eslint-config-next 16.2.6 across all apps.
eslint-config-next 16.2.6 bundles plugins (eslint-plugin-react ^7.37.0, eslint-plugin-import ^2.32.0, eslint-plugin-jsx-a11y ^6.10.0, eslint-plugin-react-hooks ^7.0.0) that do not support ESLint 10. While eslint-config-next's peer dependency spec technically permits ESLint 10 (>=9.0.0), the underlying plugins' peer dependency ranges exclude it, causing transitive conflicts and runtime errors (TypeError: contextOrFilename.getFilename is not a function). GitHub issue
#91702tracking ESLint 10 support in Next.js remains unresolved as of May 2026.This affects all 8 apps (airdrop, chain-landing, coinblast, dex, faucet, landing, scan, solux) and will break linting.
Recommendation: Hold this PR until eslint-config-next releases a version compatible with ESLint 10, or pin ESLint to ^9 until the Next.js ecosystem catches up.
🤖 Prompt for AI Agents