@pixelmatters/markup 1.18.3 → 1.18.4

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/README.md CHANGED
@@ -37,9 +37,9 @@ CDN drop-in (no build step) — paste this just before `</body>`:
37
37
  ```html
38
38
  <script type="module">
39
39
  // Pin the exact version — esm.sh resolves it from npm
40
- import { init } from 'https://esm.sh/@pixelmatters/markup@1.18.3'
40
+ import { init } from 'https://esm.sh/@pixelmatters/markup@1.18.4'
41
41
  // or
42
- // import { init } from 'https://esm.run/@pixelmatters/markup@1.18.3'
42
+ // import { init } from 'https://esm.run/@pixelmatters/markup@1.18.4'
43
43
 
44
44
  init({
45
45
  apiUrl: 'https://your-deployment.convex.site',
@@ -50,14 +50,14 @@ CDN drop-in (no build step) — paste this just before `</body>`:
50
50
  </script>
51
51
  ```
52
52
 
53
- > **Why pin the version?** CDN URLs without a version (`@pixelmatters/markup`) resolve to whatever's `latest` on npm — a future major release will break your page silently. Always pin (`@pixelmatters/markup@1.18.3`).
53
+ > **Why pin the version?** CDN URLs without a version (`@pixelmatters/markup`) resolve to whatever's `latest` on npm — a future major release will break your page silently. Always pin (`@pixelmatters/markup@1.18.4`).
54
54
 
55
55
  If your platform doesn't allow inline JS (some CMS / page-builder editors), use the auto-init form instead — point a `<script src=…>` at the bundle and pass config via `data-*` attributes:
56
56
 
57
57
  ```html
58
58
  <script
59
59
  type="module"
60
- src="https://esm.sh/@pixelmatters/markup@1.18.3"
60
+ src="https://esm.sh/@pixelmatters/markup@1.18.4"
61
61
  data-markup-widget="true"
62
62
  data-api-url="https://your-deployment.convex.site"
63
63
  data-api-key="markup_..."
@@ -323,7 +323,7 @@ If you'd rather pull it straight from the repo, or you're deciding whether to ad
323
323
  npx skills add Pixelmatters/markup/packages/widget/skills/install-markup-widget
324
324
  ```
325
325
 
326
- The path matters — it's where the skill lives in the repo, and without it the CLI picks up this repo's internal contributor skills instead.
326
+ Pass the full path, not just the repository — it's where this skill lives, and a bare repository reference resolves to a different set of skills.
327
327
 
328
328
  Otherwise, paste the block below into Claude, ChatGPT, Cursor, or any other LLM and it'll wire the widget into your codebase end-to-end.
329
329
 
@@ -370,7 +370,7 @@ For a `<script>` tag drop-in (no bundler), use the inline ESM form and **pin the
370
370
 
371
371
  ```html
372
372
  <script type="module">
373
- import { init } from 'https://esm.sh/@pixelmatters/markup@1.18.3'
373
+ import { init } from 'https://esm.sh/@pixelmatters/markup@1.18.4'
374
374
 
375
375
  init({
376
376
  apiUrl: '...',
@@ -386,7 +386,7 @@ If inline JS is disallowed (some CMS / page-builder editors), use the auto-init
386
386
  ```html
387
387
  <script
388
388
  type="module"
389
- src="https://esm.sh/@pixelmatters/markup@1.18.3"
389
+ src="https://esm.sh/@pixelmatters/markup@1.18.4"
390
390
  data-markup-widget="true"
391
391
  data-api-url="..."
392
392
  data-api-key="..."
@@ -428,15 +428,9 @@ Only `img-src` degrades gracefully: a blocked avatar falls back to initials, and
428
428
 
429
429
  Modern evergreen browsers (Chrome, Edge, Firefox, Safari) and their mobile equivalents. The widget uses native ESM, shadow DOM, and `IntersectionObserver` — no IE11 / legacy bundle.
430
430
 
431
- ## Development
431
+ ## Self-hosting Markup
432
432
 
433
- ```bash
434
- pnpm dev # vite dev server with the playground page
435
- pnpm build # production build → dist/widget.{js,d.ts}
436
- pnpm typecheck # tsc --noEmit
437
- ```
438
-
439
- To test against a local Convex deployment, pass the printed `convex.site` URL as `apiUrl`.
433
+ The widget talks to a Markup deployment; `apiUrl` is where yours lives. If you're running your own rather than using a hosted project, the backend, the dashboard and the deployment steps are in the [project repository](https://github.com/Pixelmatters/markup).
440
434
 
441
435
  ## License
442
436
 
package/dist/widget.js CHANGED
@@ -7499,7 +7499,7 @@ function Dc({ apiUrl: e, apiKey: t, position: n = "bottom-right", screenshots: r
7499
7499
  onOpenPrivacy: () => C("privacy"),
7500
7500
  onOpenShortcuts: () => C("shortcuts"),
7501
7501
  onHideForSession: () => Ce({ type: "hide-with-toast" }),
7502
- version: "1.18.3",
7502
+ version: "1.18.4",
7503
7503
  dashboardUrl: i
7504
7504
  })
7505
7505
  }) : null,
@@ -7596,11 +7596,11 @@ function jc(e, t) {
7596
7596
  a.className = "markup-shadow-root", r.appendChild(a), je({
7597
7597
  apiUrl: t.apiUrl,
7598
7598
  apiKey: t.apiKey,
7599
- widgetVersion: "1.18.3"
7599
+ widgetVersion: "1.18.4"
7600
7600
  }), be(t.analytics === !1 ? null : {
7601
7601
  apiUrl: t.apiUrl,
7602
7602
  apiKey: t.apiKey,
7603
- widgetVersion: "1.18.3"
7603
+ widgetVersion: "1.18.4"
7604
7604
  }), F("widget_loaded");
7605
7605
  let { theme: o, analytics: s, ...c } = t;
7606
7606
  return de(/* @__PURE__ */ Q(Ce, {