How does this skill handle expired authentication tokens?

It includes a client-side interceptor that automatically attempts to refresh the access token via the AuthService on a 401 error before retrying the original request.

How are cookies handled in server-side requests?

The serverFetch utility automatically extracts cookies from next/headers and forwards them to internal API routes to maintain session state during server-side rendering.

Does this work with Next.js App Router?

Yes, it is specifically designed for the Next.js App Router, supporting Client Components, Server Components, and Server Actions.

Can I use this with backend frameworks other than FastAPI?

While optimized for FastAPI patterns (like specific error detail structures), the core architecture is highly flexible and can be adapted for any RESTful backend.

Next.js Fetch Architecture

Name: Next.js Fetch Architecture
Author: adelabdelgawad

byadelabdelgawad

Desarrollo de API

Implements a robust fetch utility layer for Next.js applications communicating with FastAPI backends.

Acerca de

This skill provides a standardized architecture for data fetching in Next.js, bridging the gap between client components, server actions, and FastAPI backend services. It includes pre-configured utilities for handling authentication tokens across layers, automatic token refreshing on 401 errors, and a consistent error handling pattern. By implementing this architecture, developers can ensure secure and efficient communication between the browser, Next.js server-side logic, and external API services while maintaining type safety and robust retry logic.

Características Principales

Layered fetch utilities for Client Components, Server Actions, and API Routes
Standardized ApiError handling with descriptive error extraction
0 GitHub stars
Built-in retry logic for rate-limiting (429) and service unavailable (503) status codes
Automated authentication token refresh and session management
Full TypeScript support for end-to-end type safety in data requests

Casos de Uso

Creating SWR-compatible fetchers with automatic 401 handling
Implementing SSR data fetching using server actions with cookie forwarding
Setting up a secure proxy between a Next.js frontend and a FastAPI backend

Acerca de

Características Principales

Layered fetch utilities for Client Components, Server Actions, and API Routes
Standardized ApiError handling with descriptive error extraction
0 GitHub stars
Built-in retry logic for rate-limiting (429) and service unavailable (503) status codes
Automated authentication token refresh and session management
Full TypeScript support for end-to-end type safety in data requests

Casos de Uso

Creating SWR-compatible fetchers with automatic 401 handling
Implementing SSR data fetching using server actions with cookie forwarding
Setting up a secure proxy between a Next.js frontend and a FastAPI backend