Skip to content
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

Jump to bottom

[feature]: add a no-stale option to allow sending stale value #856

Closed
1 task done
yassilah opened this issue Jan 20, 2023 · 0 comments · Fixed by #857
Closed
1 task done

[feature]: add a no-stale option to allow sending stale value #856

yassilah opened this issue Jan 20, 2023 · 0 comments · Fixed by #857
Labels
pending triage

Comments

@yassilah
Copy link
Contributor

yassilah commented Jan 20, 2023 •
edited
Loading

Describe the feature

Currently, SWR option works great but it would be great to allow sending a stale value, while updating the cache in the background to avoid any downtime or timeout requests when querying large amounts of data. It also allows deploying to Vercel on the Hobby plan, which has a 10s task execution limit, while still querying updated data in the background 😊

Additional information

  • Would you be willing to help implement this feature?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
pending triage
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: support staleMaxAge: -1 to always respond stale value yassilah/nitro
1 participant
@yassilah