Local dev setup missing shows 706–988 — seed.sql outdated
Nobody has claimed this yet.
- Dominant language
- Svelte
- Stars
- 1.2k
- Forks
- 515
- Avg merge
- 23h
- Merged PRs (30d)
- 13
Description
The seed file (seed/seed.sql) only contains data up to show 705. On a fresh local setup, after running pnpm dev, only those shows are available until the admin import endpoint is manually triggered to sync the rest from the markdown files.
This creates a poor onboarding experience for new contributors — the site works but is missing ~280 episodes. It also makes it harder to investigate bugs affecting newer shows, for example syntaxfm/website#2170 (host names missing for shows featuring w3cj) was difficult to reproduce locally because those shows (742+) aren't in the seed data.
Two possible fixes:
- Update
seed.sqlperiodically to include newer shows — low-tech but requires manual upkeep - Auto-import from markdown on first run —
preheat.jsalready has all the logic viaimport_or_update_all_changed_shows(), it could call that instead of (or after) seeding when the table is empty. Since all shows exist as.mdfiles in the repo, no DB credentials or network access needed
Option 2 seems more maintainable long-term since the markdown files are always up to date in the repo.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with seed/seed.sql and preheat.js, especially import_or_update_all_changed_shows(), then inspect how pnpm dev initializes the local database and how the admin import endpoint is invoked. Decide how first-run initialization should load the markdown shows without network access, and verify that a fresh setup includes shows beyond 705, including those around 742.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100