Skip to content

fix: Next.js 16 compatibility issues#29

Merged
SuveenE merged 7 commits into
FoloUp:mainfrom
brijeshmarch16:fix/nextjs16-compatibility
Jan 28, 2026
Merged

fix: Next.js 16 compatibility issues#29
SuveenE merged 7 commits into
FoloUp:mainfrom
brijeshmarch16:fix/nextjs16-compatibility

Conversation

@brijeshmarch16

@brijeshmarch16 brijeshmarch16 commented Jan 27, 2026

Copy link
Copy Markdown
Contributor

Update codebase to work with Next.js 16 breaking changes:

  • Remove unused res parameter from API route handlers (App Router only accepts request parameter)
  • Update page props to use Promise types for params/searchParams
  • Use React's use() hook to unwrap async props in client components
  • Rename middleware.ts to proxy.ts (Next.js 16 naming convention)
  • Make Clerk auth calls async with await
  • Add --webpack flag to dev/build scripts (opt out of Turbopack)
  • Update tsconfig.json for Next.js 16 compatibility
  • Remove the eslint and config the biome
  • Update the clerk to latest version

What I test after migration

  • Login, Signup
  • Create interviewer, Retell interviewers
  • Live interview

Update codebase to work with Next.js 16 breaking changes:

- Remove unused `res` parameter from API route handlers (App Router
  only accepts request parameter)
- Update page props to use Promise types for params/searchParams
- Use React's use() hook to unwrap async props in client components
- Rename middleware.ts to proxy.ts (Next.js 16 naming convention)
- Make Clerk auth calls async with await
- Add --webpack flag to dev/build scripts (opt out of Turbopack)
- Update tsconfig.json for Next.js 16 compatibility

Affected components:
- 6 API routes (create-interview, generate-insights, register-call,
  generate-interview-questions, get-call, response-webhook)
- 2 dynamic pages (interviews/[interviewId], call/[interviewId])
- Middleware/proxy configuration
- Build configuration
@SuveenE

SuveenE commented Jan 28, 2026

Copy link
Copy Markdown
Member

Thanks for the huge PR @brijeshmarch16 ! Really appreciate it.

@SuveenE

SuveenE commented Jan 28, 2026

Copy link
Copy Markdown
Member

Will it possible for you to add testing steps you followed in the description as well. @brijeshmarch16

@SuveenE SuveenE self-requested a review January 28, 2026 08:00
@SuveenE SuveenE merged commit 2480744 into FoloUp:main Jan 28, 2026
1 check passed
vchart050-max pushed a commit to vchart050-max/FoloUp that referenced this pull request Apr 20, 2026
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.

2 participants