[WIP] Migrate project to Next.js 16 and update AI SDK dependencies

[Copilot]

Migration from Next.js 15.3.4 to 16.0.3 and AI SDK 4.x to 5.x

Current State

• Next.js: 15.3.4
• AI SDK (ai): 4.3.16
• @ai-sdk/react: 1.2.12
• @ai-sdk/google: 1.2.19
• @ai-sdk/openai: 1.3.22
• @openrouter/ai-sdk-provider: 0.4.6

Target Versions

• Next.js: 16.0.3 (latest stable)
• AI SDK (ai): 5.0.97 (latest stable)
• @ai-sdk/react: 2.0.97
• @ai-sdk/google: 2.0.39
• @ai-sdk/openai: 2.0.69

Migration Plan Checklist

Phase 1: Research & Documentation ✓

• Identify current versions
• Identify target versions
• Understand project structure
• Review Next.js 16 migration guide
• Review AI SDK 5.x migration guide
• Identify breaking changes

Phase 2: Pre-Migration Setup

• Document baseline build status (network issues present)
• Identify all API routes using AI SDK
• Identify all components using AI SDK React hooks

Phase 3: Dependency Updates

• Update Next.js to 16.0.3
• Update React/React-DOM if needed
• Update AI SDK core to 5.0.97
• Update @ai-sdk/react to 2.0.97
• Update @ai-sdk/google to 2.0.39
• Update @ai-sdk/openai to 2.0.69
• Update @openrouter/ai-sdk-provider if needed
• Update eslint-config-next to match Next.js version

Phase 4: Code Changes for Breaking Changes

• Update next.config.ts for Next.js 16 changes
• Update API routes for AI SDK 5.x changes
• Update React hooks usage for @ai-sdk/react 2.x
• Fix TypeScript errors
• Update imports if needed

Phase 5: Build & Validation

• Run pnpm build successfully
• Fix any remaining TypeScript errors
• Verify no runtime warnings
• Test all configurations

Phase 6: Final Verification

• Run code review
• Run security scan (CodeQL)
• Document all changes made
• Provide summary of breaking changes handled

Original prompt

Project Migration Request: Next.js 16 + AI SDK Update

Objective:
Migrate the current project to Next.js 16 and update all AI SDK dependencies to their latest versions, ensuring zero breakage with minimal code changes.

Requirements:

1. Package Manager: Using pnpm throughout
2. Target Versions:

• Next.js 16 (latest stable)
• AI SDK (latest stable from Vercel)

1. Success Criteria:

• Successful production build (pnpm build)
• All existing functionality preserved
• No runtime errors
• No breaking changes unhandled

Migration Process:

Phase 1: Research & Planning

• Search and review official migration guides:
  • Next.js 16 migration documentation (https://nextjs.org/docs)
  • AI SDK migration/upgrade guides (https://ai-sdk.dev/docs/introduction)
• Identify all breaking changes between current and target versions
• Document deprecated features and their replacements
• Create a comprehensive migration checklist

Phase 2: Dependency Analysis

• Audit current package.json for all Next.js and AI SDK related packages
• Identify version-specific dependencies and peer dependencies
• Check for conflicting packages that may need updates

Phase 3: Incremental Migration

• Update dependencies in stages (not all at once)
• Handle breaking changes systematically:
  • Configuration changes (next.config.js/ts)
  • API route updates
  • App Router changes (if applicable)
  • AI SDK provider/model configurations
  • Type definitions and imports
• Preserve existing functionality at each step

Phase 4: Code Refactoring

• Apply minimal necessary code changes
• Update deprecated API calls to new equivalents
• Ensure type safety throughout
• Maintain code structure where possible

Phase 5: Validation

• Run pnpm build to verify production build
• Check for TypeScript errors
• Validate all configurations
• Document any warnings that need addressing

Constraints:

• Make the minimum number of changes necessary
• Do NOT refactor code unnecessarily
• Do NOT change project structure unless required by migration
• Preserve all existing features and behaviors
• Use web search extensively for official documentation and migration patterns

Deliverable:

• Complete migration with passing build
• Summary of all changes made
• List of breaking changes handled
• Green light confirmation when ready for local testing

Instructions:

1. Start with thorough web searches for migration documentation
2. Use sequential thinking - plan before executing
3. Handle each breaking change explicitly
4. Test build after each major change
5. Do not stop until migration is 100% complete and build succeeds
6. Trust your process but verify each step

Please confirm you understand the requirements and begin the migration process.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.