jamdesk 1.1.133 → 1.1.134
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.134",
|
|
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",
|
|
@@ -71,7 +71,22 @@ export function Widget({
|
|
|
71
71
|
const resolvedBase = slug ? `https://${slug}.jamdesk.app${prefix}` : '';
|
|
72
72
|
|
|
73
73
|
useEffect(() => {
|
|
74
|
-
if (!resolvedBase)
|
|
74
|
+
if (!resolvedBase) {
|
|
75
|
+
// No project slug in this context, so there's no canonical
|
|
76
|
+
// <slug>.jamdesk.app origin to bind the trigger to (see resolvedBase
|
|
77
|
+
// above). That's the normal state in local `jamdesk dev`, which runs a
|
|
78
|
+
// single project with no slug — the deployed multi-tenant build gets the
|
|
79
|
+
// slug from middleware's x-project-slug header. Without this line the
|
|
80
|
+
// button looks broken: no script, no click listener, and nothing in the
|
|
81
|
+
// console. Surface a one-line hint instead. Never fires in production,
|
|
82
|
+
// where the slug is always set.
|
|
83
|
+
console.info(
|
|
84
|
+
"[Jamdesk Widget] Live demo is inert here — the trigger binds to " +
|
|
85
|
+
"https://<slug>.jamdesk.app and only runs on the deployed docs site, " +
|
|
86
|
+
"not in local `jamdesk dev`.",
|
|
87
|
+
);
|
|
88
|
+
return;
|
|
89
|
+
}
|
|
75
90
|
const triggerSel = trigger ?? `#${buttonId}`;
|
|
76
91
|
|
|
77
92
|
// Idempotent guard. React Strict Mode double-invokes effects (mount →
|