Skip to content

api.ts hardcodes cache: "no-store" inside request(), so no fetch through this module can ever use Next.js ISR/fetch caching #189

Closed

Description

@chonilius

Every live-data fetch in the app funnels through src/lib/api.ts#request():

async function request<T>(path: string, init?: RequestInit): Promise<T> {
  const res = await fetch(`${API_BASE_URL}${path}`, {
    ...init,
    headers: { "Content-Type": "application/json", ...init?.headers },
    cache: "no-store",
  });
  ...
}

cache: "no-store" is hardcoded with no per-call override, so fetchBounties,
fetchMilestones, fetchMaintenancePools, and fetchReputationByUsername — used by
/issues, /milestones, and /reputation/[handle], none of which are dashboards — are
unconditionally opted out of Next.js's fetch caching and ISR, forcing a full server round
trip to mergefi-backend on every single request to those pages, even for content that
changes relatively slowly (a bounty's title/description, a milestone's name).

This is a broader, lower-level root cause than dashboard-specific fetch parallelization —
it's baked into the one shared helper every Server Component fetcher calls through, so no
call site can opt into a revalidate window even if it wanted to.

Suggested fix: accept an optional revalidate/cache override in request()'s init
parameter (defaulting to no-store for safety) so pages that can tolerate slightly stale
data can opt into { next: { revalidate: 30 } } instead of forcing no-store everywhere.

Activity

  1. added
    performancePerformance/optimization issue
    architectureArchitecture/design issue
    bugSomething isn't working
    very hardVery difficult task, expert-level effort required
    on Aug 21, 2026
  2. Sajjadd-dev commented on Aug 24, 2026

    @Sajjadd-dev

    @Sajjadd-dev has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hello, I’d like to contribute to this issue and would appreciate the opportunity to work on it. Thank you.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Sajjadd-dev to this issue.

  3. Abulbayty commented on Aug 24, 2026

    @Abulbayty

    @Abulbayty has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hello, I’m confident that my skills and experience make me a strong fit for this task. I’m ready to deliver quality results, and I’d appreciate the opportunity to handle it.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Abulbayty to this issue.

  4. Adewumi99 commented on Aug 24, 2026

    @Adewumi99

    @Adewumi99 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hello Maintainer, I'd love to take this on and submit a clean solution.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Adewumi99 to this issue.

  5. dee-john commented on Aug 24, 2026

    @dee-john

    @dee-john has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hi, I'd like to work on this issue! because I am very conversant with solving problems like this!

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @dee-john to this issue.

  6. Isihaq123 commented on Aug 24, 2026

    @Isihaq123

    @Isihaq123 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    I will like to work on this issues

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Isihaq123 to this issue.

  7. Binismail77 commented on Aug 24, 2026

    @Binismail77

    @Binismail77 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hello, I’d like to contribute to this issue. I have experience building and debugging full-stack applications, so I’m confident I can investigate the problem, implement the fix, and test the complete flow.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Binismail77 to this issue.

  8. naobadiah01 commented on Aug 24, 2026

    @naobadiah01

    @naobadiah01 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hello, I am a fullstack developer with years of experience building web3 and web3 applications, I have reviewed the issue and the project, please assign me this issue. ETA 1hr

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @naobadiah01 to this issue.

  9. doctorlight0 commented on Aug 24, 2026

    @doctorlight0

    @doctorlight0 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    The issue is clear to me, and I’m confident I can address the requirements with a reliable and well-structured solution.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @doctorlight0 to this issue.

  10. Temi-suwa18 commented on Aug 24, 2026

    @Temi-suwa18
    Contributor

    @Temi-suwa18 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    I have review the task and i can work on it

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Temi-suwa18 to this issue.

  11. drips-wave commented on Aug 24, 2026

    @drips-wave

    Congratulations, @Temi-suwa18! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

    🧑‍💻 @Temi-suwa18: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  12. drips-wave commented on Aug 24, 2026

    @drips-wave

    This issue has been completed by @Temi-suwa18 as part of the Stellar Wave Program's 8th Wave 🥳

    😎 @Temi-suwa18: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

  13. added a commit that references this issue on Oct 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programarchitectureArchitecture/design issuebugSomething isn't workingperformancePerformance/optimization issuevery hardVery difficult task, expert-level effort required

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions