From f716902580fe37d0a53ea94afec79d15b9e71c3b Mon Sep 17 00:00:00 2001
From: David Gwilliam <dhgwilliam@gmail.com>
Date: Mon, 22 Jun 2026 00:02:32 -0700
Subject: [PATCH] fix: handle null data in browseWavs, add HTTP status check

Avoid 'Cannot read properties of null (reading error)' when server
returns null or non-JSON. Also check resp.ok before parsing JSON.
---
 web/ui/app.js | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/web/ui/app.js b/web/ui/app.js
index 7f7e980..fe7c542 100644
--- a/web/ui/app.js
+++ b/web/ui/app.js
@@ -202,9 +202,13 @@ async function browseWavs() {
 
   try {
     const resp = await fetch(`${API}/list-wavs?dir=${encodeURIComponent(dir)}`);
+    if (!resp.ok) {
+      list.innerHTML = '<span class="no-files">HTTP ' + resp.status + '</span>';
+      return;
+    }
     const data = await resp.json();
-    if (data.error) {
-      list.innerHTML = '<span class="no-files">Error: ' + data.error + '</span>';
+    if (!data || data.error) {
+      list.innerHTML = '<span class="no-files">Error: ' + (data && data.error ? data.error : 'server error') + '</span>';
       return;
     }
     if (!Array.isArray(data) || data.length === 0) {