From f5f7214625689816e3a2395e6b5f3e0236411247 Mon Sep 17 00:00:00 2001 From: Enrico Piovesan Date: Thu, 15 Oct 2026 14:18:42 -0600 Subject: [PATCH] docs(questions): Node.js Q&A re-verified on traverse-embedder-web@0.15.0 Co-Authored-By: Claude Opus 5.5 --- .../questions/can-i-run-traverse-capabilities-in-nodejs.astro | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/questions/can-i-run-traverse-capabilities-in-nodejs.astro b/src/pages/questions/can-i-run-traverse-capabilities-in-nodejs.astro index 1bbdc1c..2597a30 100644 --- a/src/pages/questions/can-i-run-traverse-capabilities-in-nodejs.astro +++ b/src/pages/questions/can-i-run-traverse-capabilities-in-nodejs.astro @@ -51,7 +51,7 @@ const relatedLinks = [ 
{nodeExample}
-

We ran this shape on Node 20 with traverse-embedder-web@0.14.0 from npm and the traverse-starter bundle checked into the traverse repo. The submit came back accepted, the subscriber saw capability_invoked then capability_result, and traceList returned one completed trace for traverse-starter.process. No traverse-cli serve sidecar was running. The published package is now 0.15.0 and still exports NodeFsBundleLoader. That Node 20 run was not repeated against 0.15.0 for this page.

+

We ran this shape on Node 20 with traverse-embedder-web@0.15.0 from npm and the traverse-starter bundle checked into the traverse repo. The submit came back accepted, the subscriber saw capability_invoked then capability_result, and traceList returned one completed trace for traverse-starter.process. No traverse-cli serve sidecar was running.

Where this is useful