Workers SDK Issue Reports

← Back to Dashboard

#3174 Querying the list of Pages projects is very slow

Recommendation:NEEDS VERIFICATION
Difficulty:n/a
Reasoning:

Optimization request not implemented; lacks performance data and engagement after 2.5 years

Suggested Action:

Ask reporter if still relevant and for concrete performance data

Analysis Report

Issue Review: cloudflare/workers-sdk#3174

Summary

Request to optimize Pages project listing by using a faster API endpoint (/overview) instead of the current /projects endpoint.

Findings

  • Created: 2023-05-10
  • Updated: 2025-10-30
  • Version: 2.X → 4.60.0 (current)
  • Component: Pages (wrangler)
  • Labels: bug, pages
  • Comments: 0

Key Evidence

  • Issue is an internal improvement request, not a user-reported bug with reproduction steps. The body suggests moving to /overview API but provides no specific timing data or user impact.

  • Current implementation still uses /projects endpoint: The listProjects() function in packages/wrangler/src/pages/projects.ts (lines 55-73) continues to use /accounts/${accountId}/pages/projects with pagination (page size 10).

  • No PRs or changelog entries reference this issue: No merged PRs mention #3174, and the changelog has no entries for this optimization.

  • No recent activity addressing this: The file has had 7 commits since the issue was created, but none addressed the API endpoint change. Most recent changes were for compliance regions, telemetry, and refactoring.

  • Issue is over 2.5 years old with zero community engagement: No comments, no +1s, no additional context provided.

  • Low priority internal enhancement: This appears to be a self-filed enhancement request by a team member, not a critical bug affecting users.

Recommendation

Status: NEEDS VERIFICATION

Reasoning: The issue is a valid optimization request that hasn't been implemented. However, it lacks concrete performance data (how slow is "slow"?), user impact assessment, and details about the /overview API's availability/compatibility. The zero engagement suggests this may not be a significant pain point for users.

Action: Ask the reporter (or team) to provide:

  1. Current performance baseline with the /projects endpoint
  2. Expected improvement with /overview endpoint
  3. Whether /overview API is still the recommended approach after 2.5 years
  4. If this is still a priority, convert to a properly scoped enhancement issue

Suggested Comment

This issue has been open for over 2.5 years without activity. Before proceeding, we'd like to understand:

  1. Is the /overview API still the recommended approach for improving list performance?
  2. Do we have any data on the current performance impact (response times, user complaints)?
  3. Is this optimization still a priority given other Pages work?

If there's no response or this is no longer relevant, we'll close this issue in 30 days. Please feel free to reopen with updated context if needed.

Notes & Feedback (0)

No notes yet.

Add Note