chore(deps-dev): bump the tooling group across 1 directory with 3 updates#85
chore(deps-dev): bump the tooling group across 1 directory with 3 updates#85dependabot[bot] wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (9)
✅ Files skipped from review due to trivial changes (4)
🚧 Files skipped from review as they are similar to previous changes (5)
📝 WalkthroughWalkthroughThis PR updates development dependency versions across the monorepo. ESLint is upgraded from version 9 to 10 in eight application package.json files (airdrop, chain-landing, coinblast, dex, faucet, landing, scan, and solux). Additionally, the root package.json updates Turbo from version 2.3.3 to 2.9.14. Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/airdrop/package.json`:
- Line 36: The package.json currently upgrades the "eslint" dependency to "^10",
which is incompatible with eslint-config-next 16.2.6 and its bundled plugins;
revert or pin "eslint" to a 9.x range (e.g. "^9") in the "eslint" entry in
package.json for this app (and apply the same change to the other apps: airdrop,
chain-landing, coinblast, dex, faucet, landing, scan, solux) so linting uses
ESLint 9 until eslint-config-next and its plugins support ESLint 10; update
package.json's "eslint" value and run install/lint to verify no transitive
plugin errors occur.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 731b4b45-c515-45d7-918d-0dbf3d320473
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (9)
apps/airdrop/package.jsonapps/chain-landing/package.jsonapps/coinblast/package.jsonapps/dex/package.jsonapps/faucet/package.jsonapps/landing/package.jsonapps/scan/package.jsonapps/solux/package.jsonpackage.json
| "@types/react": "^19", | ||
| "@types/react-dom": "^19", | ||
| "eslint": "^9", | ||
| "eslint": "^10", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check for peer dependency conflicts with ESLint 10 in Next.js apps
echo "=== Checking eslint-config-next version ==="
rg -n "eslint-config-next" --type=json -g 'apps/*/package.json'
echo -e "\n=== Checking current ESLint versions ==="
rg -n '"eslint":\s*"\^?[0-9]' --type=json -g 'apps/*/package.json'
echo -e "\n=== Simulating npm install to check peer dependencies ==="
echo "ESLint 10 with eslint-config-next 16.2.6 will produce warnings like:"
echo "WARN eslint-plugin-react@7.37.5 requires eslint@^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7 but ESLint 10.x is installed"
echo "WARN eslint-plugin-import@2.32.0 requires eslint@^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8 || ^9 but ESLint 10.x is installed"
echo "WARN eslint-plugin-jsx-a11y@6.10.2 requires eslint@^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9 but ESLint 10.x is installed"
echo "WARN eslint-plugin-react-hooks@7.0.1 requires eslint@^3.0.0 || ... || ^9.0.0 but ESLint 10.x is installed"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:
- 1: Add support for
eslintv10ineslint-config-nextvercel/next.js#91702 - 2: When I'm trying to build my NextJs project i'm getting an error related to ESLint dependency. vercel/next.js#51744
- 3: Support @next/eslint-plugin-next > 15 eslint-config/airbnb-extended#42
🏁 Script executed:
# Check if there are any newer versions of eslint-config-next that might support ESLint 10
# Also look at the actual plugin versions bundled with 16.2.6
cd /tmp
curl -s https://registry.npmjs.org/eslint-config-next/16.2.6 2>/dev/null | python3 -c "
import sys, json
try:
data = json.load(sys.stdin)
print('=== eslint-config-next 16.2.6 Info ===')
print('Peer Dependencies:')
if 'peerDependencies' in data:
for dep, spec in data['peerDependencies'].items():
print(f' {dep}: {spec}')
print('\nDependencies:')
if 'dependencies' in data:
for dep, spec in data['dependencies'].items():
if 'eslint-plugin' in dep or dep == 'eslint':
print(f' {dep}: {spec}')
except Exception as e:
print(f'Could not fetch from npm: {e}')
" 2>/dev/null || echo "NPM registry fetch not available in sandbox"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:
- 1: Add support for
eslintv10ineslint-config-nextvercel/next.js#91702 - 2: fix: attempt to make eslint-config-next support v10 vercel/next.js#90068
- 3: https://eslint.org/blog/2026/05/eslint-v10.3.0-released/
- 4: ESLint v10 compatibility jsx-eslint/eslint-plugin-react#3977
- 5: [Feature] Support for ESLint v10 vercel/next.js#89727
Critical: 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 #91702 tracking 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
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/airdrop/package.json` at line 36, The package.json currently upgrades
the "eslint" dependency to "^10", which is incompatible with eslint-config-next
16.2.6 and its bundled plugins; revert or pin "eslint" to a 9.x range (e.g.
"^9") in the "eslint" entry in package.json for this app (and apply the same
change to the other apps: airdrop, chain-landing, coinblast, dex, faucet,
landing, scan, solux) so linting uses ESLint 9 until eslint-config-next and its
plugins support ESLint 10; update package.json's "eslint" value and run
install/lint to verify no transitive plugin errors occur.
…ates Bumps the tooling group with 3 updates in the / directory: [turbo](https://github.com/vercel/turborepo), [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) and [eslint](https://github.com/eslint/eslint). Updates `turbo` from 2.9.12 to 2.9.14 - [Release notes](https://github.com/vercel/turborepo/releases) - [Changelog](https://github.com/vercel/turborepo/blob/main/RELEASE.md) - [Commits](vercel/turborepo@v2.9.12...v2.9.14) Updates `@types/node` from 25.7.0 to 25.8.0 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) Updates `eslint` from 9.39.4 to 10.4.0 - [Release notes](https://github.com/eslint/eslint/releases) - [Commits](eslint/eslint@v9.39.4...v10.4.0) --- updated-dependencies: - dependency-name: "@types/node" dependency-version: 25.8.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: tooling - dependency-name: eslint dependency-version: 10.4.0 dependency-type: direct:development update-type: version-update:semver-major dependency-group: tooling - dependency-name: turbo dependency-version: 2.9.14 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: tooling ... Signed-off-by: dependabot[bot] <support@github.com>
f5c2dd3 to
6d28897
Compare
Bumps the tooling group with 3 updates in the / directory: turbo, @types/node and eslint.
Updates
turbofrom 2.9.12 to 2.9.14Release notes
Sourced from turbo's releases.
... (truncated)
Commits
fc62fe0publish 2.9.14 to registryfb8c9aechore: Release 2.9.13 (#12803)e8e629dfix: Avoid project-local Yarn during detection (#12801)91c90cbfix: Harden VS Code extension command execution (#12800)84f4508fix: Validate auth callback state (#12802)1779ad7Removed unneeded import form hash creation script in docs (#12799)71f8c90test: Validate lockfiles without dependency downloads (#12789)5fcb960ci: Scope GitHub Actions caches by branch (#12788)4cf9fabci: Usepull_requestfor PR title linting (#12787)859c629fix: Restore docs mobile menu (#12782)Updates
@types/nodefrom 25.7.0 to 25.8.0Commits
Updates
eslintfrom 9.39.4 to 10.4.0Release notes
Sourced from eslint's releases.
... (truncated)
Commits
452c40110.4.0b6417e8Build: changelog update for 10.4.06616856chore: upgrade knip to v6 (#20875)d13b084ci: ensure auto-created PRs run CI (#20860)7e52a71docs: add mention of@eslint-react/eslint-plugin(#20869)e71c7afci: bump pnpm/action-setup from 6.0.5 to 6.0.7 (#20862)544c0c3fix: escape code path DOT labels in debug output (#20866)db3468bdocs: tweak wording around ambiguous CJS-vs-ESM config (#20865)d84393dtest: add unit tests for SuppressionsService.applySuppressions() (#20863)9084664docs: Update READMESummary by CodeRabbit