frames: import insert from the shared @solidjs/web instance (dedup)

The reveal-boundary binding imported `insert` from the runtime source
(@dom-expressions/runtime/src/client.js), which bundled a SECOND copy of
`insert` and the reconcile/render machinery it drags in into frames/dist — ~4kb
the app already has from compiled JSX (frame-client.js itself never used the
runtime `insert`, so nothing pulled it in before). Import it from @solidjs/web
instead — the same shared instance compiled output uses — and mark @solidjs/web
external in the frames client (prod + dev) rollup entries. Client bundle back to
baseline (119.3kb -> 115.6kb). Frame tests unchanged.

Author: ryansolid

packages/solid-web/frames/src/client.ts

@@ -20,7 +20,12 @@ import {
   sharedConfig
 } from "solid-js";
 import type { Element as SolidElement } from "solid-js";
-import { insert } from "@dom-expressions/runtime/src/client.js";
+// `insert` MUST resolve to the shared @solidjs/web instance the compiled app
+// already uses — importing it from the runtime source instead bundles a second
+// copy of `insert` and the reconcile/render machinery it drags in (~4kb the app
+// already has). Kept external in rollup.config.js for the same reason the
+// server-functions/client import below is.
+import { insert } from "@solidjs/web";
 import {
   createFrame,
   createFrameElement,

packages/solid-web/rollup.config.js

@@ -201,6 +201,7 @@ export default [
     ],
     external: [
       "solid-js",
+      "@solidjs/web",
       "seroval",
       "seroval-plugins/web",
       "@solidjs/web/server-functions/client"
@@ -228,6 +229,7 @@ export default [
     ],
     external: [
       "solid-js",
+      "@solidjs/web",
       "seroval",
       "seroval-plugins/web",
       "@solidjs/web/server-functions/client"