fix(devtools): handle transient RPC failures in getOptions/telemetryEvent (#1072)

Author: antfubot

packages/devtools/client/composables/storage-options.ts

@@ -22,11 +22,23 @@ function getTabOptions<T extends keyof NuxtDevToolsOptions>(tab: T): ToRefs<Nuxt
       watchDebounced(
         source,
         async (options) => {
-          rpc.updateOptions(tab, options)
+          // Best-effort persistence: a transient RPC failure here (e.g. the
+          // connection was torn down and re-established after a dev-server
+          // reload) shouldn't surface as an uncaught error — the next change
+          // will simply retry the write.
+          rpc.updateOptions(tab, options).catch((error) => {
+            console.error(`[nuxt-devtools] Failed to persist "${String(tab)}" options`, error)
+          })
         },
         { deep: true, flush: 'post', debounce: 500, maxWait: 1000 },
       )
     })
+    .catch((error) => {
+      // Same as above: don't let a transient disconnect (e.g. right after a
+      // Nuxt dev-server reload) throw an uncaught error — fall back to the
+      // in-memory defaults already seeded above and keep the UI usable.
+      console.error(`[nuxt-devtools] Failed to load "${String(tab)}" options`, error)
+    })
 
   return refs
 }

packages/devtools/client/composables/telemetry.ts

@@ -16,5 +16,10 @@ export function telemetry(event: string, payload?: object, immediate = false) {
     osVersion: userAgentInfo.os.version,
     deviceType: userAgentInfo.device.type,
     ...payload,
-  }, immediate)
+  }, immediate).catch((error) => {
+    // Telemetry is best-effort: a transient RPC failure (e.g. the connection
+    // was torn down and re-established after a dev-server reload) should
+    // never surface to the user as an uncaught error.
+    console.error('[nuxt-devtools] Failed to send telemetry event', error)
+  })
 }