Chore/deps 06 12 25

[LGLabGreg]

Note

Upgrade React to 19.2.1 and refresh tooling/dependencies (Vite 7.2.6, Vitest 4.0.15, eslint-config-next 16.0.7, types, etc.) across root, docs, playground, and package.

• Root:
  • Bump pnpm to 10.24.0; update dev tooling: vite 7.2.6, vitest 4.0.15 (+ coverage), @vitejs/plugin-react 5.1.1, typescript-eslint 8.48.1, jsdom 27.2.0, eslint-config-next 16.0.7, @changesets/*.
• Apps/docs:
  • Upgrade react/react-dom to 19.2.1 and react-hook-form 7.68.0.
  • Update deps: @vercel/analytics 1.6.1, eslint-config-next 16.0.7, lucide-react 0.556.0, tailwind-merge 3.4.0.
  • Refresh types: @types/*.
• Apps/playground:
  • Upgrade react/react-dom to 19.2.1; update vite 7.2.6, @vitejs/plugin-react 5.1.1, and @types/*.
• Package packages/react-qr-code:
  • Align dev deps with workspace: react 19.2.1, vite 7.2.6, typescript-eslint 8.48.1, @vitejs/plugin-react 5.1.1, updated @types/*.
• Lockfile:
  • Regenerated to reflect all dependency upgrades.

^{Written by Cursor Bugbot for commit c072544. This will update automatically on new commits. Configure here.}

Summary by CodeRabbit

• Chores
  • Updated project dependencies and development tools across all packages, including React, TypeScript, Vite, and testing frameworks to latest stable versions.

_{✏️ 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	Preview	Comments	Updated (UTC)
reactqrcode-com	Ready	Preview	Comment	Dec 6, 2025 7:51am

[coderabbitai]

Walkthrough

Dependency version updates across the monorepo's package.json files, including minor and patch bumps for react, react-dom, vite, @vitejs/plugin-react, type definitions, and related tooling. Root package.json packageManager updated from pnpm@10.20.0 to pnpm@10.24.0.

Changes

Cohort / File(s)	Summary
Root & workspace configuration package.json	Updated packageManager to pnpm@10.24.0; bumped devDependencies including react/react-dom (^19.2.0 → ^19.2.1), @changesets/cli/changelog-github, @types/node, @vitejs/plugin-react, vitest, @vitest/coverage-v8, typescript-eslint, vite, lint-staged, jsdom, and eslint-config-next.
App package configurations apps/docs/package.json, apps/playground/package.json	Updated react/react-dom, @types/* (node, react, react-dom), @vitejs/plugin-react, vite, and additional tooling dependencies (docs includes lucide-react, react-hook-form, tailwind-merge, @vercel/analytics).
Workspace package packages/react-qr-code/package.json	Updated react/react-dom, @types/* (node, react, react-dom), @vitejs/plugin-react, typescript-eslint, and vite to latest minor/patch versions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• Verify version bumps are consistent across workspace packages
• Confirm no breaking changes in minor/patch updates (particularly for react, vite, and tooling)
• Check packageManager version is compatible with existing workflows

Possibly related PRs

• Next #272 — Updates same package.json files for dependency bumps and includes changeset for version recording
• Chore deps #87 — Performs dependency version updates across apps/playground, root, and packages/react-qr-code
• Chore/deps 09 11 25 #313 — Overlapping dependency bumps across docs, playground, and react-qr-code packages with similar tooling adjustments

Poem

🐰 Dependencies hop and bound,
Version bumps all around!
React, vite, and types align,
Monorepo working oh so fine!
Pnpm leads the way,
Fresher packages every day! 🎉

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Chore/deps 06 12 25' is vague and uses non-descriptive terms. While it references 'deps' (dependencies), it lacks clarity about what was updated and uses a date format that doesn't convey meaningful information about the changeset.	Use a more descriptive title like 'Chore: Update dependencies across workspace' or 'Chore: Bump dependency versions (React 19.2.1, Vite 7.2.6, TypeScript-ESLint 8.48.1, etc.)' to clearly communicate the scope of dependency updates.

✅ 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.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/deps-06-12-25

---

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: 0

🧹 Nitpick comments (1)

package.json (1)

47-47: Consider using a caret range for @vitest/coverage-v8.

@vitest/coverage-v8 is pinned at exactly 4.0.15 (no caret or tilde). Other devDependencies use caret ranges. If this pinning is intentional (to avoid coverage instability), document the reason; otherwise, consider updating to ^4.0.15 to allow patch updates.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bee6cba and c072544.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (4)

• apps/docs/package.json (1 hunks)
• apps/playground/package.json (1 hunks)
• package.json (2 hunks)
• packages/react-qr-code/package.json (1 hunks)

🔇 Additional comments (7)

apps/docs/package.json (2)

55-56: Verify React 19 compatibility for the docs app.

React 19 introduces breaking changes: deprecated APIs have been removed (e.g., propTypes, defaultProps for function components, string refs, legacy Context API), ref is now a regular prop, and error handling behavior changed. Ensure the docs app does not rely on any removed or deprecated APIs and validate against React 19 breaking changes.

Also verify that the Next.js version in use is compatible with eslint-config-next@16.0.7.

Also applies to: 69-70

---

49-49: Confirm Next.js version matches eslint-config-next.

eslint-config-next@16.0.7 is tied to Next.js 16. Verify the docs app's Next.js version is 16.x to avoid eslint rule mismatches or incompatibilities.

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

52-61: Verify library code compatibility with React 19 devDependency.

The package lists React 19.2.1 as a devDependency while peerDependencies permits both React ^18 and ^19. Although the peer range supports both versions, ensure the library's code is tested and compatible with React 19 breaking changes (ref callbacks, async Request APIs, removed APIs, error handling changes). Run the build and any tests with React 19.2.1 to confirm no regressions.

Additionally, per React 19 documentation, eslint-plugin-react-hooks must be v6+. Verify the root package.json includes this version requirement.

apps/playground/package.json (1)

13-14: Verify React 19 and Vite 7 compatibility for the playground app.

React 19.2.1 and Vite 7.2.6 introduce changes that may affect the playground. Test the playground with React 19 to ensure no breaking changes (ref handling, hooks, deprecated APIs) and verify Vite 7.x build behavior. The playground is a critical testing ground for the library.

Also applies to: 18-21, 24-24

package.json (3)

8-8: pnpm version update is safe.

The packageManager bump from pnpm@10.20.0 to pnpm@10.24.0 is a minor version update. Verify all developers and CI environments update to this version to ensure consistent lockfile generation and dependency resolution.

---

57-62: Verify React 19 and tooling updates work end-to-end.

Root devDependencies now include React 19.2.1, vite 7.2.6, vitest 4.0.15, and typescript-eslint 8.48.1. These are significant tooling updates that affect build, test, and lint pipelines.

• Run the full test suite (pnpm test) to verify vitest 4.0.15 and jsdom 27.2.0 compatibility.
• Build the library (pnpm build:lib) and test apps to confirm Vite 7.2.6 works as expected.
• Lint the codebase (pnpm lint) to ensure typescript-eslint 8.48.1 and eslint-config-next 16.0.7 have no breaking rule changes.

---

65-66: Verify eslint-config-next 16.0.7 integration with root eslint setup.

The root package.json now includes eslint-config-next@16.0.7 as a dependency (not devDependency). Ensure this does not conflict with other eslint configs or rules defined in the root eslint.config.js. Confirm that eslint-config-next 16.0.7 is compatible with the root project structure and any custom lint rules.