deps(web): bump the node-dependencies group in /apps/web with 5 updates#3
Conversation
Bumps the node-dependencies group in /apps/web with 5 updates: | Package | From | To | | --- | --- | --- | | [react](https://github.com/facebook/react/tree/HEAD/packages/react) | `19.2.4` | `19.2.7` | | [react-dom](https://github.com/facebook/react/tree/HEAD/packages/react-dom) | `19.2.4` | `19.2.7` | | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `20.19.42` | `25.9.2` | | [eslint](https://github.com/eslint/eslint) | `9.39.4` | `10.4.1` | | [typescript](https://github.com/microsoft/TypeScript) | `5.9.3` | `6.0.3` | Updates `react` from 19.2.4 to 19.2.7 - [Release notes](https://github.com/facebook/react/releases) - [Changelog](https://github.com/react/react/blob/main/CHANGELOG.md) - [Commits](https://github.com/facebook/react/commits/v19.2.7/packages/react) Updates `react-dom` from 19.2.4 to 19.2.7 - [Release notes](https://github.com/facebook/react/releases) - [Changelog](https://github.com/react/react/blob/main/CHANGELOG.md) - [Commits](https://github.com/facebook/react/commits/v19.2.7/packages/react-dom) Updates `@types/node` from 20.19.42 to 25.9.2 - [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.1 - [Release notes](https://github.com/eslint/eslint/releases) - [Commits](eslint/eslint@v9.39.4...v10.4.1) Updates `typescript` from 5.9.3 to 6.0.3 - [Release notes](https://github.com/microsoft/TypeScript/releases) - [Commits](microsoft/TypeScript@v5.9.3...v6.0.3) --- updated-dependencies: - dependency-name: react dependency-version: 19.2.7 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: node-dependencies - dependency-name: react-dom dependency-version: 19.2.7 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: node-dependencies - dependency-name: "@types/node" dependency-version: 25.9.2 dependency-type: direct:development update-type: version-update:semver-major dependency-group: node-dependencies - dependency-name: eslint dependency-version: 10.4.1 dependency-type: direct:development update-type: version-update:semver-major dependency-group: node-dependencies - dependency-name: typescript dependency-version: 6.0.3 dependency-type: direct:development update-type: version-update:semver-major dependency-group: node-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
📝 WalkthroughWalkthroughUpdated ChangesDependency and Dev Tooling Updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
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/web/package.json`:
- Around line 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.
🪄 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: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 52aef5b0-0e60-49a3-a323-46a4a176b08a
📒 Files selected for processing (1)
apps/web/package.json
| "@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" |
There was a problem hiding this comment.
🧩 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/webRepository: 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:
- 1: Bump TypeScript to 6.0 vercel/next.js#91257
- 2: vercel/next.js@d141874
- 3: vercel/next.js@aa3ba7e
- 4: Don't suppress usage of deprecated TypeScript
compilerOptionsvercel/next.js#93377 - 5: [ESLint v10]: TypeError: contextOrFilename.getFilename is not a function when running ESLint v10 vercel/next.js#89764
Regenerate apps/web/bun.lock and constrain TypeScript for the Next.js lint stack.
apps/web/bun.lockstill resolves older tooling (e.g.,eslint@9.39.4) and does not show the expectedeslint@10.x/typescript@6.xpins fromapps/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.9is not a reliable default for ESLint 10. typescript-eslint@8.61.0(present in the lockfile) requirestypescript >=4.8.4 <6.1.0, so keep TypeScript on6.0.x(avoid6.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.
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
mors119
deleted the
dependabot/npm_and_yarn/apps/web/node-dependencies-794d197ad1
branch
1 participant
Bumps the node-dependencies group in /apps/web with 5 updates:
19.2.419.2.719.2.419.2.720.19.4225.9.29.39.410.4.15.9.36.0.3Updates
reactfrom 19.2.4 to 19.2.7Release notes
Sourced from react's releases.
Commits
6117d7cVersion 19.2.7 (#36591)eaf3e95Version 19.2.623f4f9f19.2.5Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for react since your current version.
Updates
react-domfrom 19.2.4 to 19.2.7Release notes
Sourced from react-dom's releases.
Commits
6117d7cVersion 19.2.7 (#36591)eaf3e95Version 19.2.623f4f9f19.2.5Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for react-dom since your current version.
Updates
@types/nodefrom 20.19.42 to 25.9.2Commits
Updates
eslintfrom 9.39.4 to 10.4.1Release notes
Sourced from eslint's releases.
... (truncated)
Commits
4a3d15a10.4.143e7e2bBuild: changelog update for 10.4.1e557467fix: update@eslint/plugin-kitversion to 0.7.2 (#20930)b0e466btest: adddataproperty to invalid tests cases for rules (#20924)d4ce898fix: propagate failures from delegated commands (#20917)f4f3507fix: prefer-arrow-callback invalid autofix with newline afterasync(#20916)f78838btest: add CodePath type coverage (#20904)61b0adddocs: remove deprecated rule from related rules ofmax-params(#20921)1daa4bdchore: updateeslint-plugin-eslint-commentstest data to latest commit (#20...002942cci: declare contents:read on update-readme workflow (#20919)Updates
typescriptfrom 5.9.3 to 6.0.3Release notes
Sourced from typescript's releases.
Commits
050880cBump version to 6.0.3 and LKGeeae9dd🤖 Pick PR #63401 (Also check package name validity in...) into release-6.0 (#...ad1c695🤖 Pick PR #63368 (Harden ATA package name filtering) into release-6.0 (#63372)0725fb4🤖 Pick PR #63310 (Mark class property initializers as...) into release-6.0 (#...607a22aBump version to 6.0.2 and LKG9e72ab7🤖 Pick PR #63239 (Fix missing lib files in reused pro...) into release-6.0 (#...35ff23d🤖 Pick PR #63163 (Port anyFunctionType subtype fix an...) into release-6.0 (#...e175b69Bump version to 6.0.1-rc and LKGaf4caacUpdate LKG8efd7e8Merge remote-tracking branch 'origin/main' into release-6.0Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsSummary by CodeRabbit