@pixelmatters/markup 1.15.0 → 1.16.0

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
@@ -35,9 +35,9 @@ CDN drop-in (no build step) — paste this just before `</body>`:
35
35
  ```html
36
36
  <script type="module">
37
37
  // Pin the exact version — esm.sh resolves it from npm
38
- import { init } from 'https://esm.sh/@pixelmatters/markup@1.15.0'
38
+ import { init } from 'https://esm.sh/@pixelmatters/markup@1.16.0'
39
39
  // or
40
- // import { init } from 'https://esm.run/@pixelmatters/markup@1.15.0'
40
+ // import { init } from 'https://esm.run/@pixelmatters/markup@1.16.0'
41
41
 
42
42
  init({
43
43
  apiUrl: 'https://your-deployment.convex.site',
@@ -48,14 +48,14 @@ CDN drop-in (no build step) — paste this just before `</body>`:
48
48
  </script>
49
49
  ```
50
50
 
51
- > **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.15.0`).
51
+ > **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.16.0`).
52
52
 
53
53
  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:
54
54
 
55
55
  ```html
56
56
  <script
57
57
  type="module"
58
- src="https://esm.sh/@pixelmatters/markup@1.15.0"
58
+ src="https://esm.sh/@pixelmatters/markup@1.16.0"
59
59
  data-markup-widget="true"
60
60
  data-api-url="https://your-deployment.convex.site"
61
61
  data-api-key="markup_..."
@@ -271,7 +271,7 @@ For a `<script>` tag drop-in (no bundler), use the inline ESM form and **pin the
271
271
 
272
272
  ```html
273
273
  <script type="module">
274
- import { init } from 'https://esm.sh/@pixelmatters/markup@1.15.0'
274
+ import { init } from 'https://esm.sh/@pixelmatters/markup@1.16.0'
275
275
 
276
276
  init({
277
277
  apiUrl: '...',
@@ -287,7 +287,7 @@ If inline JS is disallowed (some CMS / page-builder editors), use the auto-init
287
287
  ```html
288
288
  <script
289
289
  type="module"
290
- src="https://esm.sh/@pixelmatters/markup@1.15.0"
290
+ src="https://esm.sh/@pixelmatters/markup@1.16.0"
291
291
  data-markup-widget="true"
292
292
  data-api-url="..."
293
293
  data-api-key="..."