Skip to content

deps(web): bump the node-dependencies group in /apps/web with 5 updates #3

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.

Sign up for GitHub

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

Closed
dependabot wants to merge 1 commit into from
Closed

deps(web): bump the node-dependencies group in /apps/web with 5 updates #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions apps/web/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,18 +10,18 @@
},
"dependencies": {
"next": "16.2.9",
"react": "19.2.4",
"react-dom": "19.2.4"
"react": "19.2.7",
"react-dom": "19.2.7"
},
"devDependencies": {
"@tailwindcss/postcss": "^4",
"@types/node": "^20",
"@types/node": "^25",
"@types/react": "^19",
"@types/react-dom": "^19",
"eslint": "^9",
"eslint": "^10",
"eslint-config-next": "16.2.9",
"tailwindcss": "^4",
"typescript": "^5"
"typescript": "^6"
Comment on lines +18 to +24

@coderabbitai coderabbitai Bot Jun 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify lockfile update and check for compatibility issues

# Check if lockfile has been updated with new versions
echo "=== Checking lockfile for new versions ==="
rg '"react".*19\.2\.7' apps/web/bun.lock
rg '"typescript".*6\.' apps/web/bun.lock
rg '"eslint".*10\.' apps/web/bun.lock

# Check Next.js peer dependencies or version constraints
echo -e "\n=== Checking Next.js package info ==="
cat apps/web/node_modules/next/package.json 2>/dev/null | jq '.peerDependencies, .engines' || echo "node_modules not available in sandbox"

# Look for any TypeScript or ESLint config issues
echo -e "\n=== Checking for config files ==="
fd -e json -e js 'tsconfig|eslint' apps/web

Repository: FrilLab/frilchain

Length of output: 8151

🌐 Web query:

Does Next.js 16.2.9 support TypeScript 6.0 and eslint 10?

💡 Result:

As of June 10, 2026, Next.js 16.2.9 supports TypeScript 6.0, but does not provide full native support for ESLint 10 in its default configuration. TypeScript 6.0: Next.js officially integrated support for TypeScript 6.0 in the 16.2 development cycle [1][2]. This includes updates to internal tsconfig defaults and the removal of deprecated compiler options that were incompatible with TypeScript 6.0 behaviors [3][4]. Users are encouraged to migrate projects to align with these newer TypeScript standards rather than relying on framework-level rewiring [4]. ESLint 10: Next.js (specifically the eslint-config-next package) does not yet offer full, native support for ESLint 10 [5]. As of June 2026, users attempting to use ESLint 10 often encounter runtime errors due to dependency incompatibilities, particularly with packages like eslint-plugin-react that rely on legacy APIs removed in ESLint 10 [5]. While community workarounds and temporary fixes (such as manually specifying the React version in the ESLint configuration) exist, official stability for ESLint 10 within the Next.js linting stack remains pending [5]. For stable production environments, it is currently recommended to continue using ESLint 9 [5].

Citations:

Regenerate apps/web/bun.lock and constrain TypeScript for the Next.js lint stack.

  • apps/web/bun.lock still resolves older tooling (e.g., eslint@9.39.4) and does not show the expected eslint@10.x / typescript@6.x pins from apps/web/package.json, so CI may not actually receive the upgraded majors until the lockfile is regenerated.
  • The lint stack is sensitive here: eslint-config-next@16.2.9 is not a reliable default for ESLint 10.
  • typescript-eslint@8.61.0 (present in the lockfile) requires typescript >=4.8.4 <6.1.0, so keep TypeScript on 6.0.x (avoid 6.1+).

After regenerating the lockfile (bun install), run bun run lint and bun run build.

🤖 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/web/package.json` around lines 18 - 24, The lockfile (apps/web/bun.lock)
still pins older tooling and doesn't reflect the updated majors in package.json
(e.g., "eslint": "^10", "typescript": "^6") and the lint stack compatibility
with eslint-config-next@16.2.9; regenerate the lockfile by running bun install
in apps/web, then ensure TypeScript is constrained to 6.0.x (not 6.1+) to
satisfy typescript-eslint@8.61.0's ">=4.8.4 <6.1.0" requirement, update
package.json if needed to pin "typescript" to "6.0.x", and after regenerating
run bun run lint and bun run build to verify ESLint 10 and the Next lint stack
work with the new lockfile.

},
"ignoreScripts": [
"sharp",
Expand Down
Loading