jamdesk 1.1.77 → 1.1.78

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jamdesk",
-  "version": "1.1.77",
+  "version": "1.1.78",
   "description": "CLI for Jamdesk — build, preview, and deploy documentation sites from MDX. Dev server with hot reload, 50+ components, OpenAPI support, AI search, and Mintlify migration",
   "keywords": [
     "jamdesk",

package/vendored/lib/render-doc-page.tsx

@@ -451,13 +451,20 @@ export async function renderDocPage(input: RenderInput): Promise<ReactElement> {
     }
   }
 
-  logger.info('[render-timing]', {
-    region: process.env.VERCEL_REGION || 'unknown',
-    pagePath,
-    snippetInlineMs,
-    openApiMs,
-    openApiCandidates,
-  });
+  // Gate on VERCEL_REGION so the telemetry only fires in Vercel runtime
+  // (production + preview). In `jamdesk dev` the structured JSON would
+  // pollute the user's terminal on every page render. `[r2-timing]` logs
+  // are kept out of CLI dev by stubbing `lib/r2-content.ts`; this is the
+  // equivalent guard for `[render-timing]`, which has no R2 dependency.
+  if (process.env.VERCEL_REGION) {
+    logger.info('[render-timing]', {
+      region: process.env.VERCEL_REGION,
+      pagePath,
+      snippetInlineMs,
+      openApiMs,
+      openApiCandidates,
+    });
+  }
 
   let mdxApiMethod: HttpMethod | null = null;
   let mdxApiPath: string | null = null;