feat: update to storybook v10 and antfu-config to 6.1

[ixartz]

BREAKING CHANGE: update to Next.js 16

Summary by CodeRabbit

• Chores
  • Updated development and production dependencies to latest stable versions, including updates to testing frameworks, build tools, code quality utilities, and core packages for improved compatibility and maintenance.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
next-js-boilerplate	Ready	Preview	Comment	Oct 28, 2025 4:00pm

[coderabbitai]

Walkthrough

Multiple dependency versions are updated in package.json, including posthog-js, Storybook packages, Vitest packages, ESLint plugins, and other development tooling. No changes to public APIs or exported entities.

Changes

Cohort / File(s)	Change Summary
Main Dependencies package.json	posthog-js updated from 1.280.1 to 1.281.0
Storybook Ecosystem package.json	@storybook/addon-a11y, @storybook/addon-docs, @storybook/addon-vitest, @storybook/nextjs-vite, eslint-plugin-storybook, and storybook all updated from 9.1.15 to 9.1.16
Vitest Ecosystem package.json	@vitest/browser, @vitest/browser-playwright, @vitest/coverage-v8, vitest updated from 4.0.3 to 4.0.4; vitest-browser-react updated from 2.0.0 to 2.0.2
ESLint & Code Quality package.json	@antfu/eslint-config updated from 6.0.0 to 6.1.0; @eslint-react/eslint-plugin from 2.2.3 to 2.2.4; @next/eslint-plugin-next from 15.5.6 to 16.0.0
Other Tools package.json	@spotlightjs/spotlight from 4.2.0 to 4.3.0; @types/pg from 8.15.5 to 8.15.6; drizzle-kit from 0.31.5 to 0.31.6; knip from 5.66.2 to 5.66.4

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• This PR contains only version bumps in package.json with no logic changes, code alterations, or API modifications
• All changes are homogeneous and repetitive in nature (dependency updates across multiple packages)

Possibly related PRs

• fix: upgrade to Next.js 15.3 #377: Updates multiple overlapping packages (posthog-js, @next/eslint-plugin-next, drizzle-kit) in the same manifest file
• fix: update to Next.js 15.5 #452: Contains similar dependency-only updates with overlapping package bumps (posthog, vitest-browser-react, Next-related tooling)
• fix: update antfu config to version 5 #471: Includes updates to @antfu/eslint-config and other shared development dependencies

Poem

🐰 Dependencies dance in a version ballet,
From 1.280 to fresh heights they sway,
Storybook shines, Vitest takes the stage,
Tools and plugins turn the page,
Package.json blooms—hip hip hooray! 🎉

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title Check	⚠️ Warning	The PR title claims to update "storybook v10," but the actual changeset shows storybook being updated from 9.1.15 to 9.1.16, which is a patch release within the v9 major version, not an upgrade to v10. The title's claim about the antfu-config update to 6.1 is accurate (@antfu/eslint-config: 6.0.0 -> 6.1.0). While the PR does include numerous other dependency updates (including Next.js to v16), the primary claim about Storybook v10 is factually incorrect and misleading about the actual scope of changes being made.	The title should be corrected to accurately reflect the actual changes, such as "feat: update storybook to 9.1.16 and antfu-config to 6.1" or similar wording that correctly represents the Storybook version being deployed. If the intention was to update to Storybook v10, the changeset needs to be updated to reflect that major version upgrade instead of the current v9 patch update.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-storybook10

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ccda0f6 and d119dba.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Run E2E tests (22.x)
• GitHub Check: Run Storybook (22.x)
• GitHub Check: GitHub PR synchronize with Crowdin
• GitHub Check: Run unit tests (22.x)

🔇 Additional comments (2)

package.json (2)

1-120: ---

PR title is inaccurate: Storybook remains at v9.1.16 (patch update), not v10.

Storybook v10 is not released, making the PR title's claim to "update to storybook v10" incorrect. The actual changes only update Storybook and related packages (lines 65–68, 89, 98) from v9.1.15 to v9.1.16—a patch-level release within the v9 major version.

Tooling compatibility confirmed. @next/[email protected] has peer dependencies satisfied by next@^16.0.0, react@^19.2.0, react-dom@^19.2.0, and storybook@^9.1.16, indicating no compatibility issues with the rest of the dependency tree.

Action required: Clarify whether the Storybook v10 upgrade was intended but incomplete, or if the PR title should be corrected to reflect the actual v9.1.16 patch updates.

Likely an incorrect or invalid review comment.

---

45-45: No compatibility issues found. Package versions are correctly aligned.

Verification confirms the updated packages have consistent versioning:

• Next.js 16.0.0 correctly paired with @next/eslint-plugin-next 16.0.0
• Storybook ecosystem (9.1.16) components properly aligned
• Vitest ecosystem (4.0.4) all at matching versions

The "UNMET DEPENDENCY" messages in npm ls are expected in a sandbox environment without node_modules installed. No actual peer dependency conflicts or breaking changes were detected.

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 6.00%. Comparing base (ccda0f6) to head (d119dba).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@          Coverage Diff          @@
##            main    #481   +/-   ##
=====================================
  Coverage   6.00%   6.00%           
=====================================
  Files         44      44           
  Lines        283     283           
  Branches      42      42           
=====================================
  Hits          17      17           
  Misses       239     239           
  Partials      27      27           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

🎉 This PR is included in version 6.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀