jamdesk 1.1.50 → 1.1.51
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "jamdesk",
|
|
3
|
-
"version": "1.1.
|
|
3
|
+
"version": "1.1.51",
|
|
4
4
|
"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",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"jamdesk",
|
|
@@ -309,9 +309,14 @@ export async function DocsChrome({
|
|
|
309
309
|
<link rel="dns-prefetch" href="https://cdn.segment.com" />
|
|
310
310
|
)}
|
|
311
311
|
{/*
|
|
312
|
-
|
|
313
|
-
|
|
312
|
+
Project-subdomain hydration-error + dev-overlay suppression.
|
|
313
|
+
Gated to production so the inline <script> doesn't trigger React
|
|
314
|
+
19's "scripts inside React components are never executed when
|
|
315
|
+
rendering on the client" warning in `jamdesk dev`. The IIFE
|
|
316
|
+
itself already self-gates to non-localhost subdomains, so dev
|
|
317
|
+
was a no-op — gating the JSX is pure dev-console cleanup.
|
|
314
318
|
*/}
|
|
319
|
+
{process.env.NODE_ENV === 'production' && (
|
|
315
320
|
<script
|
|
316
321
|
dangerouslySetInnerHTML={{
|
|
317
322
|
__html: `
|
|
@@ -370,6 +375,7 @@ export async function DocsChrome({
|
|
|
370
375
|
`,
|
|
371
376
|
}}
|
|
372
377
|
/>
|
|
378
|
+
)}
|
|
373
379
|
{/*
|
|
374
380
|
precedence + stable href lets React 19 hoist these into <head> as
|
|
375
381
|
managed resources and dedupe across renders, so theme/font styles
|