Show HN: Dirsv – live reload server for dir browsing, GFM, and more filetypes
I write a lot of markdown in Neovim — learning notes with KaTeX math, design docs with Mermaid/D2 diagrams, cross ... I also browse repos offline and preview static sites. No single tool handled all of that with live reload. So I built dirsv. It's a single Go binary with an embedded web UI, use fsnotify for watching filesystem, and send WebSocket events to reload the browser page. I also build dirsv.nvim that auto start dirsv at repo root (or current working dir if it's not a git repo), then ope
Read original sourceSource record
Recorded metrics
points · 1 votes
2026-11-06 22:15:22.566Z
cumulative since publication
Research analysis
Project record
Repository: letientai299/dirsv. Source account: I write a lot of markdown in Neovim — learning notes with KaTeX math, design docs with Mermaid/D2 diagrams, cross ... I also browse repos offline and preview static sites. No single tool handled all of that with live reload. So I built dirsv. It's a single Go binary with an embedded web UI, use fsnotify for watching filesystem, and send WebSocket events to reload the browser page. I also build dirsv.nvim that auto start dirsv at repo root (or current working dir if it's not a git repo), then ope
Observed adoption & comparisons
Source votes: 1 votes (Nov 6, 2026 UTC; cumulative since publication); previous same-scope observation: 1 (Nov 6, 2026 UTC). These observations do not establish demand growth. Recent records to compare: “Show HN: ViewFit – Resize images to the size they are rendered at” (Show HN, Nov 6, 2026); “JiaFeiMiao-K-Cat/DiscImageStudio” (GitHub Trending, Nov 6, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.
Adoption decision
Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.
Unverified requirements
Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.
Next test
Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.