Next

[LGLabGreg]

Summary by CodeRabbit

• Chores
  • Updated development dependencies to latest stable versions across multiple packages, including TypeScript types, ESLint configuration, Vite, and testing utilities.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
reactqrcode-com	Ready	Preview, Comment	Jan 16, 2026 7:11am

[coderabbitai]

Walkthrough

This PR updates devDependency and dependency versions across three package.json files in the monorepo, including TypeScript types (@types/node, @types/react), build tools (vite, eslint-config-next, next), and other development dependencies. No functional code changes or API modifications are made.

Changes

Cohort / File(s)	Summary
Dependency Version Updates apps/docs/package.json, package.json, packages/react-qr-code/package.json	Updates multiple devDependency versions across three package.json files: @types/node, @types/react, globals, vite, typescript-eslint, eslint-config-next, next, react-hook-form, @trivago/prettier-plugin-sort-imports, and Vitest-related packages to minor/patch version increments. No runtime dependencies altered.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Chore deps #87: Synchronized dependency version bumps in packages/react-qr-code with overlapping packages (@types/node, @types/react, globals, vite).
• Chore/deps 12 12 25 #389: Concurrent dependency version updates across the same three package.json files (apps/docs, root, packages/react-qr-code).
• Chore/deps 06 12 25 #373: Overlapping devDependency bumps in the same package.json files with shared packages (eslint-config-next, @types/node, @types/react).

Poem

🐰 Hop, hop, versions rise with care,
Dependencies updated everywhere,
TypeScript types and build tools bright,
Keeping the monorepo tight! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Next' is vague and does not convey meaningful information about the changeset, which consists entirely of dependency version updates across multiple package.json files.	Consider a more descriptive title that reflects the actual changes, such as 'Update dependencies' or 'Bump devDependencies to latest versions'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch next

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@package.json`:
- Around line 39-59: Add a Node engine constraint to package.json by adding an
"engines" field specifying the supported Node versions ("node": "^20.19.0 ||
>=22.12.0") so the repo declares it requires Node 20.19.0+ (or 22.12.0+), and
update CI configuration files (e.g., GitHub Actions workflow matrix or other
pipeline definitions) to only run jobs on these supported Node versions; modify
package.json's top-level object to include the new "engines" key and adjust your
CI YAML/matrix entries to match the same version range.

📜 Review details

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 539a703 and 1417be2.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (3)

• apps/docs/package.json
• package.json
• packages/react-qr-code/package.json

🔇 Additional comments (3)

apps/docs/package.json (1)

34-41: Looks good—please validate docs app build with Next 16 + react-hook-form bump.
I’d just confirm next build/next lint still pass after the major Next upgrade.

Also applies to: 48-50

packages/react-qr-code/package.json (1)

52-61: Tooling bumps look fine—please re-run the library build.
Just verify tsc -b && vite build still succeeds with the updated toolchain.

package.json (1)

63-63: Ensure eslint-config-next 16.1.2 migration to flat config is completed.
The upgrade to 16.1.2 is a bugfix release, but if upgrading from <16.0.0, the flat config migration must be applied: run npx @next/codemod@canary upgrade latest to generate eslint.config.mjs, update lint scripts to use ESLint CLI (eslint .), and remove any eslint option from next.config.js. Verify the new config includes next/core-web-vitals and next/typescript as needed.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check for Node version constraints in the repository
echo "=== Checking for Node version files ==="
fd -H -a '^\.(nvmrc|node-version)$' -x sh -c 'echo "== {} =="; cat {}'

echo -e "\n=== Checking package.json for engines field ==="
cat -n package.json | grep -A 5 '"engines"'

echo -e "\n=== Full devDependencies section for context ==="
cat -n package.json | sed -n '39,59p'

Repository: LGLabGreg/react-qr-code

Length of output: 1016

---

🌐 Web query:

Node.js version requirements for Vite 7.3.1

💡 Result:

Vite 7.3.1 requires Node.js ^20.19.0 or >=22.12.0 (i.e., Node >=20.19.0, with support also for 22.12+). Vite no longer supports Node 18. [1][2]

Sources:
[1] vite@7.3.1 package.json (engines: "node": "^20.19.0 || >=22.12.0").
[2] Vite migration notes: "Node.js 20.19+ / 22.12+ is now required."

---

🌐 Web query:

Node.js version requirements for Vitest 4.0.17

💡 Result:

Vitest 4.0.17 requires Node.js >= 20.0.0. [1][2]

Sources:

• Vitest getting started / requirements (Node >= v20.0.0). [1]
• Snyk / package info showing latest Vitest version 4.0.17. [2]

---

🌐 Web query:

Node.js version requirements for jsdom 27.4.0

💡 Result:

jsdom 27.x requires Node.js 20+; specifically the project documents minimum supported versions as: Node.js v20.19.0 or newer on the v20 line, or v22.12.0+, or v24.0.0+. [1][2]

Sources:

• jsdom release notes (27.0.1 / 27.x). [1]
• jsdom package metadata / docs (v27.4.0). [2]

---

🌐 Web query:

Node.js version requirements for typescript-eslint 8.53.0

💡 Result:

typescript-eslint v8 (including 8.53.0) requires Node.js: ^18.18.0 || ^20.9.0 || >=21.1.0. [1][2]

Sources:

• typescript-eslint dependency versions page. [1]
• typescript-eslint v8 announcement (notes about bumped Node support). [2]

---

Document Node.js version requirement: repo must support Node 20.19.0+ (Vite 7.3.1 and jsdom 27.4.0 drop Node 18 support).

Vite 7.3.1 and jsdom 27.4.0 now require Node ≥20.19.0 or ≥22.12.0, ending Node 18 support. Add an "engines": { "node": "^20.19.0 || >=22.12.0" } field to package.json and ensure CI pipelines run only on supported versions.

🤖 Prompt for AI Agents

In `@package.json` around lines 39 - 59, Add a Node engine constraint to
package.json by adding an "engines" field specifying the supported Node versions
("node": "^20.19.0 || >=22.12.0") so the repo declares it requires Node 20.19.0+
(or 22.12.0+), and update CI configuration files (e.g., GitHub Actions workflow
matrix or other pipeline definitions) to only run jobs on these supported Node
versions; modify package.json's top-level object to include the new "engines"
key and adjust your CI YAML/matrix entries to match the same version range.