Skip to content

docs: update Next.js example to createSmoothFetch #60

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AryanSharma48 merged 1 commit into from
Sep 26, 2026
Merged

docs: update Next.js example to createSmoothFetch #60

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions examples/nextjs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ or call the routes directly with the curl commands below.

### `/api/resilient` — retry + fallback

This route points `createResilientFetch` at `/unstable-data`, which returns a
This route points `createSmoothFetch` at `/unstable-data`, which returns a
mix of `200`, `429`, and `500` responses. With the default retry settings, a
retryable status (`429`/`500`/...) causes the client to back off and try again
(up to the default number of retries). Because `/unstable-data` never fails
Expand All @@ -72,7 +72,7 @@ library does **not** fall back to its browser `alert()` behavior on the server.

### `/api/circuit-demo` — circuit breaker

This route points `createResilientFetch` at `/always-fail`, which always returns
This route points `createSmoothFetch` at `/always-fail`, which always returns
`500`, with `failureThreshold: 3` and a short `cooldownMs` so the demo is quick.

Call it repeatedly and watch the behavior change:
Expand Down
Loading