Skip to content

feat: migrate to Next.js App Router - #40

Open
akinboyewaSamson wants to merge 1 commit into
Proof-Stell:mainfrom
akinboyewaSamson:feature/app-router-migration
Open

feat: migrate to Next.js App Router#40
akinboyewaSamson wants to merge 1 commit into
Proof-Stell:mainfrom
akinboyewaSamson:feature/app-router-migration

Conversation

@akinboyewaSamson

Copy link
Copy Markdown
Contributor

closes #32

Summary
This PR successfully migrates the ProofStell frontend from the legacy Pages Router to the modern Next.js 15 App Router (src/app), ensuring alignment with our PRD architecture requirements.

Key Changes
Directory Restructuring: Migrated all UI components from src/pages to the src/app directory (e.g. src/app/page.tsx, src/app/dashboard/page.tsx).
Client Components & Routing:
Added "use client" directives to all pages requiring React state or wallet SDK interaction.
Refactored next/router hooks to standard next/navigation (useRouter, useParams).
Global Providers & Layout: Replaced _app.tsx and _document.tsx with a unified src/app/layout.tsx to handle global metadata and authentication contexts.
API Route Upgrade: Migrated existing Pages API endpoints to App Router Route Handlers (src/app/api/.../route.ts).
Metadata Update: Replaced next/head imports with native <title> tags inside the components.
Cleanup: Safely deleted the legacy src/pages directory and pnpm configuration files to standardize the workspace.
Testing
All existing dynamic routing (/documents/[id]) and authentication state management work correctly inside the new Providers layout wrapper.

@MaryammAli

Copy link
Copy Markdown
Contributor

@akinboyewaSamson this is not the issue description
please read the issue description and implement

@MaryammAli

Copy link
Copy Markdown
Contributor

@akinboyewaSamson
you have conflict ,kindly resolve

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.

Enhance API Error Handling with Centralized Error Recovery

3 participants