@artooi/ag-ui-web-component 0.14.1 → 0.15.0

package/dist/ui/render_markdown.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"render_markdown.d.ts","sourceRoot":"","sources":["../../src/ui/render_markdown.ts"],"names":[],"mappings":"AAoEA,0CAA0C;AAC1C,MAAM,WAAW,qBAAqB;IACpC;;;;OAIG;IACH,QAAQ,CAAC,WAAW,CAAC,EAAE,OAAO,CAAC;CAChC;AAED;;;;;;;;;;GAUG;AACH,wBAAgB,cAAc,CAAC,IAAI,EAAE,MAAM,EAAE,OAAO,CAAC,EAAE,qBAAqB,GAAG,MAAM,CAcpF"}
+{"version":3,"file":"render_markdown.d.ts","sourceRoot":"","sources":["../../src/ui/render_markdown.ts"],"names":[],"mappings":"AAwFA,0CAA0C;AAC1C,MAAM,WAAW,qBAAqB;IACpC;;;;OAIG;IACH,QAAQ,CAAC,WAAW,CAAC,EAAE,OAAO,CAAC;CAChC;AAED;;;;;;;;;;GAUG;AACH,wBAAgB,cAAc,CAAC,IAAI,EAAE,MAAM,EAAE,OAAO,CAAC,EAAE,qBAAqB,GAAG,MAAM,CAcpF"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@artooi/ag-ui-web-component",
-  "version": "0.14.1",
+  "version": "0.15.0",
   "description": "Framework-free <ag-ui-chat> Web Component over the AG-UI protocol. Drop-in chat sidebar with a pluggable client-side tool registry, DOM driver primitives, animations, and destructive-action confirmation modal.",
   "type": "module",
   "main": "./dist/index.js",
@@ -56,15 +56,17 @@
   "dependencies": {
     "@ag-ui/client": ">=0.0.54 <0.1",
     "@ag-ui/core": ">=0.0.54 <0.1",
-    "dompurify": "3.4.7",
+    "dompurify": "^3.4.13",
     "marked": "^18.0.4"
   },
   "devDependencies": {
     "@biomejs/biome": "^2.4.0",
     "@types/node": "^26.1.0",
+    "@vitest/browser": "^3.2.7",
     "@vitest/coverage-v8": "^3.0.0",
     "esbuild": "^0.28.1",
     "happy-dom": "^20.11.1",
+    "playwright": "^1.62.1",
     "typescript": "^5.7.0",
     "vitest": "^3.0.0"
   },

package/src/ui/render_markdown.ts

@@ -1,13 +1,33 @@
-// ⚠ ``dompurify`` is pinned at exactly 3.4.7 in package.json — not a caret
-// range. 3.4.8 through at least 3.4.13 mis-sanitise under happy-dom: the
-// sanitiser silently passes ``<script>`` and ``<img>`` straight through, which
-// this module's own tests catch. Verified again 2026-08-07 against happy-dom
-// 20.11.1, so it is not fixed by moving the test DOM forward either.
+// DOMPurify is exercised in a **real browser** by the `chromium` project in
+// vitest.config.ts, not by the happy-dom suite. That is deliberate: 3.4.8+ do
+// not sanitise under happy-dom at all — `<script>` and `<img>` pass straight
+// through — so a happy-dom-only suite can go green while this module ships no
+// sanitisation whatsoever.
 //
-// That leaves four open dompurify advisories (three LOW, one MEDIUM) knowingly
-// unpatched. The trade is deliberate: those advisories describe narrow bypasses,
-// while taking them costs *all* sanitisation under the only DOM we can test in.
-// Revisit whenever either project moves; the tests are the acceptance check.
+// **Root cause, upstream, and both are refusing to move.** DOMPurify 3.4.8
+// changed one line, reading the tag name through
+// `lookupGetter(Node.prototype, "nodeName")` instead of `currentNode.nodeName`
+// (cure53/DOMPurify 3.4.7...3.4.8). happy-dom defines an *own* `nodeName`
+// getter on **both** `Node.prototype` (returning `""`) and `Element.prototype`,
+// so grabbing the base one defeats the dispatch and every element resolves to
+// `tagName === ""`. Not in ALLOWED_TAGS, so the wrapper is stripped and its
+// children are re-inserted as clones the NodeIterator never revisits — which is
+// why nested payloads come back *entirely* unsanitised. Real browsers and jsdom
+// define `nodeName` only on `Node.prototype` and are unaffected.
+//
+//   happy-dom bug:      capricorn86/happy-dom#2182 (open)
+//   working fix:        capricorn86/happy-dom#2183 (closed, never merged)
+//   DOMPurify's answer: cure53/DOMPurify#1457, #1496 (closed, wontfix —
+//                       "happy-dom is not supported")
+//
+// ⚠ DOMPurify's README names happy-dom as **not safe**: combining them "will
+// likely lead to XSS". jsdom is the only non-browser DOM it supports. So the
+// old exact pin at 3.4.7 was never the safety it looked like — cure53 notes it
+// "doesn't really work, it just appears so". Running these assertions in
+// Chromium is the fix; the pin was a placebo.
+//
+// ⚠ If you ever move these assertions back under happy-dom to make them faster,
+// you remove the only check that this module does anything at all.
 import DOMPurify from "dompurify";
 import { Marked } from "marked";
 

package/src/version.ts

@@ -1 +1 @@
-export const VERSION: string = "0.14.1";
+export const VERSION: string = "0.15.0";