@symbiote-native/solid 0.0.1

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 A. Prokopenko
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,130 @@
+# @symbiote-native/solid
+
+SolidJS adapter for SymbioteNative. Compiled Solid JSX drives real native iOS/Android views through
+the same `@symbiote-native/engine` every other adapter uses — React's renderer is never in the path.
+
+**Status: L4 in progress (parity phase).** The renderer seam, `mount`/`unmount`, the primitives, the
+stateful touch components, the Touchable family, Button / ImageBackground / InputAccessoryView,
+StatusBar and the list family all ship at full parity with the React reference — off
+`@symbiote-native/components`, via `descriptorToSolid` where the component has a shared render fn.
+The engine-owned runtime modules are re-exported from the barrel. Still absent: `createPortal` and
+`createTunnel`, both of which need a same-surface replacement for `solid-js/web`'s DOM-bound
+`Portal`/`Dynamic`. See `symbiote-new-adapter` §7 for what each layer means and why the adapter is
+built in that order.
+
+Solid's own control-flow `Switch`/`Match` are NOT re-exported from this package: `Switch` collides
+with RN's Switch component, which every adapter must export under that name. Import the control-flow
+pair from `solid-js` directly.
+
+Publishing is gated by `"private": true` in `package.json`, which is what
+`scripts/lib/publishable-packages.mjs` filters on — so `changeset publish` and the pkg.pr.new canary
+both skip this package until that flag comes off. Without it `0.0.0` (a version absent from npm) would
+be published on the next release run, shipping a reduced surface and violating the repo's
+`<adapters_reach_full_feature_parity>` invariant. Remove the flag in the commit that finishes parity.
+
+## Why Solid needs no DOM shim and no Metro transformer
+
+Solid ships an official custom-renderer API, `createRenderer` from `solid-js/universal`. That is
+exactly the framework-agnostic seam this project looks for in every framework, so the adapter is
+`RendererOptions`' ten methods mapped onto the engine's mutation API — no shimming of private
+internals (the Svelte adapter's approach, forced by an unmerged upstream PR), no compiler running
+beside Metro (Angular's AOT), and no custom `babelTransformerPath` at all.
+
+Targets **Solid 1.9**, deliberately not 2.0 (RC as of 2026-08): 2.0 moved the package to
+`@solidjs/universal`, changed `RendererOptions` (added `createSentinel`/`cleanupNodes`, gave
+`createElement` a staticProps argument) and changed the compiled-output shape (`use()` →
+`applyRef`/`ref`, `effect(fn, init)` → `effect(fn, effectFn)`). Moving to it is a rewrite of
+`src/renderer.ts`, not a range bump.
+
+## Wiring an app
+
+`babel.config.js` — the preset ships preconfigured, so the app can't get `moduleName` or `generate`
+wrong:
+
+```js
+module.exports = {
+  presets: [
+    'module:@react-native/babel-preset',
+    // LAST on purpose: Babel applies presets in reverse order, so this runs FIRST and claims the
+    // JSX before the React Native preset's own React-JSX transform can.
+    '@symbiote-native/solid/babel-preset',
+  ],
+};
+```
+
+`metro.config.js` needs `unstable_conditionNames: ['browser']` — `solid-js`'s export map has a `node`
+branch pointing at its SSR build, and resolving that into a native bundle is the same failure mode
+the Svelte example hit (`lifecycle_function_unavailable` on the first mount).
+
+Solid compiles a component to `function App(props)` — a function with an uppercase name, which is
+exactly what react-refresh's `isLikelyComponentType` heuristic looks for. It then tries to patch a
+React Fiber tree that does not exist in this path, and the update is swallowed with no error. Force a
+full reload instead: `unstable_forceFullRefreshPatterns: [/\.tsx$/]`.
+
+## `./renderer` is a compiler target, not a convenience export
+
+`babel-preset-solid` with `generate: 'universal'` rewrites JSX into direct calls imported from the
+`moduleName` it was given. So `src/renderer.ts` exports eleven specific names because generated code
+imports them; dropping one breaks bundling with a module-not-found on an import nobody wrote. The
+list (`createElement`, `createTextNode`, `insertNode`, `insert`, `setProp`, `use`, `effect`, `memo`,
+`createComponent`, `spread`, `mergeProps`) was verified by compiling representative JSX, not read off
+the docs.
+
+## Three things the universal runtime does that the seam has to answer correctly
+
+Each is a one-line decision in `src/renderer.ts` with a real failure behind it — the comments there
+cite the runtime line that forces them.
+
+1. **`createTextNode('')` is a placeholder, not content.** The runtime parks an empty text node where
+   a dynamic expression will go. An empty `RCTRawText` genuinely paints in Fabric, so an empty string
+   maps to an engine anchor instead (skipped by the commit walk).
+2. **`isTextNode` must answer "can I write a string into this", not "did `createTextNode` make it".**
+   The runtime asks it about that placeholder anchor; answering `true` sends it to write text into a
+   node that never reaches Fabric.
+3. **Anchors stay visible to `getFirstChild`/`getNextSibling`.** The runtime re-derives positions
+   through those lookups, so hiding a node it inserted itself desyncs its bookkeeping from the tree.
+   Anchors are invisible to Fabric, not to traversal.
+
+## Typing — the app points `jsxImportSource` here, and that is the whole setup
+
+```jsonc
+// tsconfig.json
+"jsx": "preserve",
+"jsxImportSource": "@symbiote-native/solid"
+```
+
+That is all an app needs. No `/// <reference types>` line, no `solid-env.d.ts`, no per-file pragma:
+TypeScript resolves the entire JSX namespace from this package's `./jsx-runtime` entry, which is
+type-only (the emitted JS is `export {};` and nothing ever imports it — JSX becomes calls on
+`./renderer` through babel-preset-solid's `moduleName`, a separate mechanism).
+
+Two things follow that the earlier `declare module 'solid-js'` shim could not give:
+
+- **A web tag is a compile error.** `<div>` reports `TS2339: Property 'div' does not exist on type
+'JSX.IntrinsicElements'` instead of building fine and failing on device. Augmenting solid-js's
+  namespace merges into its HTML/SVG list, so `<div>` stayed legal there. The Svelte adapter needed
+  a whole preprocessor for the same guarantee.
+- **JSX children are type-checked at all.** solid-js's `JSX.Element` names the DOM's `Node`, which
+  does not resolve without a DOM lib — and `skipLibCheck` swallows that error rather than reporting
+  it, leaving `Element` as `any` and every JSX child position unchecked. The visible symptom was
+  small (a render-prop parameter needed an explicit annotation); the cause was not.
+
+The risk recorded when this was deferred — that our `Element` must line up with what solid-js's own
+`<Show>`/`<For>` return — resolves for the same reason: solid's is `any` in the DOM-less programs we
+target, so it is assignable to anything of ours. `src/jsx-runtime.test.tsx` pins the runtime half;
+the type half rides on `examples/solid`'s typecheck. Full rationale, the measurements behind each
+claim, and the one config that would break it: `.claude/rules/solid-jsx-namespace.md`.
+
+## Single root per process
+
+Compiled JSX calls module-level functions with no surface argument, so there is nowhere to thread a
+per-surface renderer through — the active surface is module state, set by `mount`. The Svelte adapter
+reached the same single-root conclusion for its own reasons.
+
+## Reference
+
+- The canary app: `examples/solid` (its README covers the tarball loop and what is verified).
+- The engine API this targets: the `symbiote-engine-core` skill, `core/engine/src/node.ts`.
+- Building/porting an adapter: the `symbiote-new-adapter` skill.
+- The nodeOps table this mirrors: `adapters/vue/src/renderer/index.ts`.
+- The same seam on an ANSI target: `wolf-tui/packages/solid/src/renderer/node-ops.ts`.

package/babel-preset.cjs

@@ -0,0 +1,41 @@
+// The Babel preset a consuming app puts in its babel.config.js:
+//
+//   presets: ['module:@react-native/babel-preset', '@symbiote-native/solid/babel-preset']
+//
+// It is babel-preset-solid with the two options that MUST be right pre-filled, so an app can
+// never get them wrong:
+//
+//   generate: 'universal'  — emit calls into a custom renderer instead of DOM operations.
+//   moduleName             — where those calls are imported FROM. Compiled JSX turns into
+//                            `import { createElement } from '<moduleName>'`, so this string has
+//                            to name a real, resolvable module exporting the 11 functions
+//                            createRenderer() returns (src/renderer.ts, published as the
+//                            ./renderer subpath). A typo here fails at bundle time with a
+//                            module-not-found on a path nobody wrote by hand.
+//
+// Same reasoning as ./metro-css-parser.cjs: shipping the wiring from the adapter means the app
+// declares no extra devDependency (babel-preset-solid is OUR dependency, and require() resolves
+// relative to this file, not via the app's node_modules).
+//
+// .cjs, not .js: this package is "type": "module", and Babel require()s a preset.
+//
+// Preset ORDER in the app matters and is not arbitrary. Babel applies presets in REVERSE array
+// order, so listing this one LAST runs it FIRST — before @react-native/babel-preset's own
+// React-JSX transform gets a chance to claim the same JSX nodes.
+module.exports = function symbioteSolidBabelPreset(_api, options = {}) {
+  return {
+    presets: [
+      [
+        require('babel-preset-solid'),
+        {
+          ...options,
+          // Last, deliberately: an app may pass other babel-preset-solid options through, but
+          // not these two — overriding either one silently produces output this adapter cannot
+          // satisfy (DOM operations, or imports from a module that exports nothing we provide).
+          generate: 'universal',
+          moduleName: '@symbiote-native/solid/renderer',
+        },
+      ],
+    ],
+  };
+};

package/metro-css-parser.cjs

@@ -0,0 +1,8 @@
+// Re-exported from THIS file's own location so a consuming app's
+// require('@symbiote-native/solid/metro-css-parser') resolves css-parser as a dependency of THIS
+// package, not the app's node_modules (Node resolves require() relative to the requiring file,
+// not via pnpm hoisting) — the app never needs to declare @symbiote-native/css-parser itself.
+// .cjs, not .js: this package is "type": "module", but Metro's babelTransformerPath loading needs
+// a require()-able file. createCssMetroTransformer() is a factory — Metro needs the actual
+// {transform, getCacheKey} object it returns, not the css-parser package barrel.
+module.exports = require('@symbiote-native/css-parser').createCssMetroTransformer();

package/package.json

@@ -0,0 +1,72 @@
+{
+  "name": "@symbiote-native/solid",
+  "version": "0.0.1",
+  "description": "SymbioteNative's Solid adapter — a solid-js/universal createRenderer driving real native iOS/Android views through the same engine as every other adapter.",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/OneEyed1366/symbiote-native.git",
+    "directory": "adapters/solid"
+  },
+  "homepage": "https://github.com/OneEyed1366/symbiote-native/tree/master/adapters/solid#readme",
+  "bugs": {
+    "url": "https://github.com/OneEyed1366/symbiote-native/issues"
+  },
+  "author": "Andrey Prokopenko <psevdoproger@gmail.com>",
+  "type": "module",
+  "main": "./build/index.js",
+  "module": "./build/index.js",
+  "types": "./build/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./build/index.d.ts",
+      "default": "./build/index.js"
+    },
+    "./bootstrap": {
+      "types": "./build/bootstrap.d.ts",
+      "default": "./build/bootstrap.js"
+    },
+    "./renderer": {
+      "types": "./build/renderer.d.ts",
+      "default": "./build/renderer.js"
+    },
+    "./jsx-runtime": {
+      "types": "./build/jsx-runtime.d.ts",
+      "default": "./build/jsx-runtime.js"
+    },
+    "./jsx-dev-runtime": {
+      "types": "./build/jsx-runtime.d.ts",
+      "default": "./build/jsx-runtime.js"
+    },
+    "./babel-preset": "./babel-preset.cjs",
+    "./metro-css-parser": "./metro-css-parser.cjs"
+  },
+  "files": [
+    "build",
+    "babel-preset.cjs",
+    "metro-css-parser.cjs"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "dependencies": {
+    "babel-preset-solid": "^1.9.12",
+    "typescript": "~6.0.0",
+    "@symbiote-native/css-parser": "0.3.0",
+    "@symbiote-native/components": "0.4.0"
+  },
+  "peerDependencies": {
+    "@symbiote-native/engine": ">=0.1.7",
+    "solid-js": ">=1.9.0",
+    "react-native": ">=0.86"
+  },
+  "devDependencies": {
+    "solid-js": "^1.9.14",
+    "@symbiote-native/engine": "0.2.0",
+    "@symbiote-native/test-utils": "0.1.6"
+  },
+  "scripts": {
+    "typecheck": "tsc --build",
+    "format": "prettier --write \"src/**/*.{ts,tsx}\""
+  }
+}