Six pages hard-code "Storage unreachable" and /b reads the store twice

Open Beginner friendly
  • Is something wrong?
#832 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
next.js, typescript
Domain
backend

Research direction

Start with upload-store.ts:60 and the listed page locations to trace the existing storage error messages. Then read b/[slug]/page.tsx:35, 52 and check how its metadata and page each call find(). Done when the short message uses the exported constant and metadata and page share one cached read.

Written by the indexing model from the issue text.

Description

night-shift web

From the 2026-11-06 web audit (W33, W15). tools/collections/page.tsx:46, 71, tools/guild-board/page.tsx:51, tools/gold-ledger/page.tsx:48, addons/[name]/page.tsx:153 and census/page.tsx:257 hard-code the short "Storage unreachable" while upload-store.ts:60 exports STORAGE_UNREACHABLE for the long form. b/[slug]/page.tsx:35, 52 runs find() twice per request (metadata and page).

Fix. Export STORAGE_UNREACHABLE_SHORT next to the long one and import it; wrap find in React cache() so metadata and page share one read. Size S.

Dominant language
TypeScript
Stars
0
Forks
0
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CDVolvik/everloot

All issues in CDVolvik/everloot

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.