@symbiote-native/svelte 3.0.3 → 3.0.4

package/build/components/virtualized-list/index.svelte

@@ -12,8 +12,7 @@
   //
   // This file authors the raw `scroll-view` intrinsic directly, and needs to: it walks an indexable
   // `plan.cells` list rather than taking an opaque children Snippet, so it can mark sticky cells
-  // itself. (There is no ScrollView component to render instead — it was deleted 2026-09-10 and an
-  // app writes the tag too.)
+  // itself. (There is no ScrollView component to render instead — an app writes the tag too.)
   //
   // It does NOT author the CONTENT node. `registerScrollViewBehavior()` puts a `buildStructure` on
   // the scroll tags, and exactly one thing may build `RCTScrollContentView` — emitting one here as

package/build/components/virtualized-section-list/index.svelte

@@ -63,12 +63,9 @@
       Platform.OS,
     ),
   );
-  // DIAGNOSTIC (2026-08-13, tracking why stickyHeaderIndices comes back undefined on Android
-  // despite the demo passing the bare `stickySectionHeadersEnabled` shorthand): the previous
-  // logging only showed the RESULT (VirtualizedList's own dlog), never the INPUTS this $derived
-  // actually read — isolated verification proved bare-shorthand forwarding through this exact
-  // two-hop generic-component chain works correctly in a standalone repro, so this must show
-  // what differs in the real component tree.
+  // Diagnostic: logs every INPUT this $derived reads, not just VirtualizedList's own result —
+  // `stickyHeaderIndices` can come back undefined on Android with the bare
+  // `stickySectionHeadersEnabled` shorthand, and only the inputs show what differs.
   $effect(() => {
     dlog(
       `VirtualizedSectionList sticky-inputs enabled=${String(props.stickySectionHeadersEnabled)} ` +

package/build/create-portal/index.js

@@ -1,9 +1,6 @@
-// Portal — the Svelte adapter's same-surface portal: the twin of React's `createPortal`
-// (adapters/react/src/create-portal/index.ts), Solid's `<Portal mount={…}>`
-// (adapters/solid/src/create-portal/index.tsx) and Angular's PortalDirective/PortalOutletDirective
-// pair. This adapter shipped `createTunnel` and no portal in any spelling until 2026-08-20; the
-// two do NOT overlap (see the table at the bottom of this header), so the tunnel was never a
-// substitute.
+// Portal — the Svelte adapter's same-surface portal: the twin of React's `createPortal`, Solid's
+// `<Portal mount={…}>` and Angular's PortalDirective/PortalOutletDirective pair. Does NOT overlap
+// with `createTunnel` (table at the bottom of this header) — the tunnel is not a substitute.
 //
 // WHY IT IS A COMPONENT (`<Portal mount={…}>`) AND NOT A CALL (`createPortal(content, target)`).
 // NOT for Solid's reason. Solid had to avoid the call form because Solid evaluates JSX eagerly at

package/build/dom-shim/patch-globals.js

@@ -2,9 +2,8 @@
 // (svelte-adapter-dom-shim skill §2, §3a, §6). Must run before `mount()` (§3f) — not
 // necessarily before `svelte` is imported.
 //
-// Single-root only, by design (§10, decided during Svelte adapter planning 2026-08-11): one
-// Symbiote app = one process = one Svelte root, so `restoreGlobals()` needs no ref-counting —
-// `unmount()` calls it unconditionally.
+// Single-root only, by design (§10): one Symbiote app = one process = one Svelte root, so
+// `restoreGlobals()` needs no ref-counting — `unmount()` calls it unconditionally.
 //
 // Deliberately NOT patched, and must stay that way (§6b, §6c, §6d) — both verified against the
 // real vendored RN source (.vendors/react-native/packages/react-native/Libraries/Core/), not
@@ -51,20 +50,9 @@ const PATCHED_KEYS = [
 // with (unlike `navigator`/`requestAnimationFrame`, verified against .vendors/react-native —
 // see the header comment above), so patching this is safe.
 //
-// `get()` returns a TRUTHY stand-in, and that is the whole reason `set_custom_element_data` can be
-// made lossless. Its condition (attributes.js:245-265) is a ternary, not a fallback:
-//
-//   setters_cache.has(nodeName) || !customElements || customElements.get(nodeName)
-//     ? get_setters(node).includes(prop)     <- a real setter decides; the value passes through
-//     : value && typeof value === 'object'   <- a HEURISTIC: an object is set as a property and
-//                                               every scalar is handed on as String(value)
-//
-// Returning `undefined` — which it did until 2026-09-07 — selects the heuristic, so
-// `<text-input multiline={false}>` committed the STRING "false" and an object-valued prop with no
-// prototype setter was assigned to a plain JS property and silently lost. Anything truthy steers
-// it to `get_setters`, which reaches `ShimElement.prototype`'s accessors (see
-// `svelte-shim-element-global-must-be-an-ancestor.md` for why that walk terminates where it does).
-// One reader in the whole client runtime, so nothing else is affected.
+// `get()` returns a TRUTHY stand-in — the whole reason `set_custom_element_data` stays lossless.
+// Falsy selects attributes.js's HEURISTIC path instead of `get_setters`: it stringifies scalars
+// and drops any object-valued prop with no prototype setter.
 const FAKE_CUSTOM_ELEMENT_REGISTRY = {
     get: () => ShimElement,
 };

package/build/index.js

@@ -4,11 +4,9 @@
 // All Fabric clone-on-write lives in the engine, shared cross-adapter. App code names only
 // @symbiote-native/svelte.
 //
-// Full component parity with React/Vue/Angular landed 2026-08-11 (svelte-adapter-dom-shim
-// skill §15): every `core/components` render function has a fixed tree shape, so no
-// `descriptorToSvelte` bridge was ever needed — each component below is hand-authored Svelte
-// markup mirroring its render-*.ts, reusing only the pure state/render logic. See skill §17/§18
-// for the one open async-exception repro and the honest cross-cutting gap list.
+// Full component parity with React/Vue/Angular (svelte-adapter-dom-shim skill §15): every
+// `core/components` render function has a fixed tree shape, so no `descriptorToSvelte` bridge is
+// needed — each component below is hand-authored Svelte markup mirroring its render-*.ts.
 // Bare side-effect import, deliberately NOT a re-export and deliberately not beside one of the
 // same specifier: it registers the press behavior with the engine's host-behavior registry. Any
 // other shape is dropped by Metro's inlineRequires in a release build — see register.ts.
@@ -25,9 +23,8 @@ export { KeyboardAvoidingView, Modal, VirtualizedList, FlatList, VirtualizedSect
 // threaded through this barrel (parity fix, see React's index.ts lines 55-58, 89, 245-250).
 export { setImageSourceResolver } from '@symbiote-native/components';
 // Pure, framework-agnostic runtime modules — same re-export every other adapter does per
-// CLAUDE.md's <runtime_modules_layering>. PanResponder was missing here (present on
-// React/Vue's own barrels) until 2026-08-12 — a pure engine re-export, no framework glue, so
-// adding it is a one-line parity fix, not new adapter work.
+// CLAUDE.md's <runtime_modules_layering>. A pure engine re-export with no framework glue, so
+// adding one is a one-line parity fix, not new adapter work.
 export { Platform, StyleSheet, PlatformColor, DynamicColorIOS, processColor, setNativeViewConfigSource, setColorProcessor, setDeviceEventSource, PixelRatio, PanResponder, dlog, isDebug, } from '@symbiote-native/engine';
 // The two namespaces left behind by primitives that became tags, here rather than in the component
 // block above for one reason: they carry no view. `Image` gets an adapter file only because it

package/build/modules/animated/index.js

@@ -9,10 +9,9 @@
 // between the value graph and the node's Fabric tag, and both of those were already engine-side.
 //
 // Those three were aliases of the wrappers, and the wrappers are gone — a primitive is a tag now,
-// which is not a value `<Animated.X>` can call. `Animated.ScrollView` left the same way on
-// 2026-09-10: `bindAnimatedEvent` (node.ts, from `setEventListener`) attaches a native-driven event
-// on ANY host node, which was the one job a scroll wrapper still looked like it had. The whole API
-// is `<scroll-view style={{ opacity: v }} p={{ onScroll: Animated.event(…) }}>`.
+// which is not a value `<Animated.X>` can call. `Animated.ScrollView` left the same way:
+// `bindAnimatedEvent` (node.ts) attaches a native-driven event on ANY host node.
+// The whole API is `<scroll-view style={{ opacity: v }} p={{ onScroll: Animated.event(…) }}>`.
 //
 // The two below REMAIN because the LIST family is tier 3: a render prop decides their output shape
 // in JS, so there is no tag for `<Animated.X>` to be an alias of.

package/build/preprocessor/collapse-text-whitespace.js

@@ -1,11 +1,8 @@
 // svelte-adapter-dom-shim skill §16: Svelte trims only the leading/trailing whitespace of a
 // fragment's own children - never whitespace INSIDE a single Text node, and never a
-// whitespace-only Text node BETWEEN two siblings. Vue's compiler (and every browser) collapses
-// both; Svelte doesn't. Confirmed against the real compiler (2026-08-17): a Text node authored
-// as `Hello world, this is a\n  long sentence.` compiles verbatim into
-// `$.text('Hello world, this is a\n  long sentence.')` - the newline and indent ship into the
-// native text content and render as a forced line break plus stray leading spaces on device.
-// Reproduced live on an iOS simulator before this file existed; fixed with it registered.
+// whitespace-only Text node BETWEEN two siblings. Vue's compiler (and every browser) collapse both.
+// A Text node authored as `Hello world, this is a\n  long sentence.` compiles verbatim, so the
+// newline and indent ship into native text as a forced line break plus stray leading spaces.
 //
 // Two hazards:
 //   1. Wrapped sentence - a Text node with real content plus an embedded whitespace run

package/build/preprocessor/forbid-web-only-constructs.js

@@ -1,4 +1,4 @@
-// §7 of svelte-adapter-dom-shim (DECIDED 2026-08-11): the constructs that compile cleanly and
+// §7 of svelte-adapter-dom-shim: the constructs that compile cleanly and
 // then silently do nothing under the DOM shim. Everything else in the original §4 table is
 // already closed by "app code can't reach it" or "the TS/Svelte compiler already errors on it for
 // free" (see the skill for the full reachability table). This preprocessor is the guard for what

package/build/preprocessor/scoped-styles.js

@@ -127,13 +127,11 @@ export function scopedStyles() {
 // ---------------------------------------------------------------------------------------------
 // The <style> block, located WITHOUT parsing it.
 //
-// This is svelte's own tag regex (src/compiler/preprocess/index.js), which is what its official
-// `preprocess()` style hook uses to hand a block's content to a preprocessor unparsed — and the
-// reason `svelte-preprocess` can compile SCSS at all. Reading `parse().css` instead, as this file
-// did until 2026-08-20, validates the block as CSS whatever `lang` says: `<style lang="scss">$pad:
-// 7px;</style>` threw `css_expected_identifier` before the language table above was ever
-// consulted, so only SCSS that is already valid CSS (nesting) survived. A `<!-- -->` comment is an
-// alternative of the pattern purely so a commented-out block is skipped rather than matched.
+// This is svelte's own tag regex (src/compiler/preprocess/index.js): what its official
+// `preprocess()` style hook uses to hand a block's content unparsed, the reason `svelte-preprocess`
+// can compile SCSS at all — `parse().css` would validate it as CSS whatever `lang` says.
+// A `<!-- -->` comment is an alternative of the pattern purely so a commented-out block is
+// skipped rather than matched.
 const STYLE_TAG_PATTERN = /<!--[^]*?-->|<style((?:\s+[^=>'"/\s]+=(?:"[^"]*"|'[^']*'|[^>\s]+)|\s+[^=>'"/\s]+)*\s*)(?:\/>|>([\S\s]*?)<\/style>)/g;
 const LANG_ATTRIBUTE_PATTERN = /\blang\s*=\s*(?:"([^"]*)"|'([^']*)'|([^\s>]+))/;
 function findStyleBlock(content) {

package/build/render.js

@@ -1,7 +1,7 @@
 // Mount a Svelte app onto a Fabric surface. The native host hands us a rootTag; we create a
 // surface for it, install the DOM shim, and let stock compiled Svelte output drive it while
-// believing it is talking to the real DOM. Decided during Svelte adapter planning
-// (2026-08-11, svelte-adapter-dom-shim skill §10): single root per process, so
+// believing it is talking to the real DOM.
+// Single root per process (svelte-adapter-dom-shim skill §10), so
 // patchGlobals()/restoreGlobals() need no ref-counting.
 import { mount as svelteMount, unmount as svelteUnmount, } from 'svelte';
 import { createSurface, disposeRoot, dlog, reportUncaughtError, } from '@symbiote-native/engine';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@symbiote-native/svelte",
-  "version": "3.0.3",
+  "version": "3.0.4",
   "description": "SymbioteNative's Svelte adapter — a DOM shim over stock compiled Svelte output driving real native iOS/Android views through the same engine as every other adapter.",
   "keywords": [
     "react-native",
@@ -73,22 +73,22 @@
   },
   "dependencies": {
     "typescript": "~6.0.0",
-    "@symbiote-native/components": "3.1.1",
-    "@symbiote-native/css-parser": "0.5.1"
+    "@symbiote-native/components": "3.1.2",
+    "@symbiote-native/css-parser": "0.5.2"
   },
   "peerDependencies": {
     "svelte": ">=5.56.0",
     "react-native": ">=0.86",
-    "@symbiote-native/engine": "^1.3.0"
+    "@symbiote-native/engine": "^1.3.1"
   },
   "devDependencies": {
     "@vue/runtime-core": "^3.5.13",
     "react": "19.2.3",
     "svelte": "^5.56.0",
-    "@symbiote-native/engine": "1.3.0",
-    "@symbiote-native/react": "3.0.3",
-    "@symbiote-native/test-utils": "0.4.3",
-    "@symbiote-native/vue": "3.0.3"
+    "@symbiote-native/engine": "1.3.1",
+    "@symbiote-native/react": "3.0.4",
+    "@symbiote-native/test-utils": "0.4.4",
+    "@symbiote-native/vue": "3.0.4"
   },
   "scripts": {
     "typecheck": "tsc --build",