Skip to content

fix: upgrade React 19 + Next.js 15 to resolve runtime error#18

Open
Minifigures wants to merge 1 commit intomainfrom
fix/react19-upgrade
Open

fix: upgrade React 19 + Next.js 15 to resolve runtime error#18
Minifigures wants to merge 1 commit intomainfrom
fix/react19-upgrade

Conversation

@Minifigures
Copy link
Copy Markdown
Owner

Summary

  • Upgraded React 18 → 19 and Next.js 14 → 15 to fix TypeError: render is not a function in updateContextConsumer — the base-nova shadcn style uses @base-ui/react which requires React 19's context API
  • Fixed duplicate keys in tailwind.config.ts (fontSize, keyframes, animation were declared twice) which caused next build to fail
  • Removed unused next-themes dependency from Toaster component — useTheme() was called without a ThemeProvider, hardcoded to "light" theme instead

Test plan

  • next build passes cleanly with zero errors
  • next dev serves pages without runtime errors
  • Backend health check returns OK
  • Verify no render is not a function error in browser console
  • Smoke test navigation across all pages

🤖 Generated with Claude Code

The base-nova shadcn style uses @base-ui/react which requires React 19's
context API. Running on React 18 caused "render is not a function" in
updateContextConsumer. Also fixes duplicate keys in tailwind.config.ts
that broke production builds, and removes unused next-themes dependency
from the Toaster component.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant