@sigx/lynx-runtime 0.4.2 → 0.4.4
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 +3 -3
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
Background-thread renderer for [SignalX](https://github.com/signalxjs) on Lynx. Translates sigx component output into the BG → MT op stream that drives the native render tree.
|
|
4
4
|
|
|
5
|
-
> Most apps should depend on [`@sigx/lynx`](
|
|
5
|
+
> Most apps should depend on [`@sigx/lynx`](https://github.com/signalxjs/lynx/tree/main/packages/lynx) instead, which re-exports this package's public surface alongside `@sigx/reactivity` and `@sigx/runtime-core` for a single import path.
|
|
6
6
|
|
|
7
7
|
## Responsibilities
|
|
8
8
|
|
|
@@ -11,12 +11,12 @@ Background-thread renderer for [SignalX](https://github.com/signalxjs) on Lynx.
|
|
|
11
11
|
- **Op queue** — `pushOp`, `scheduleFlush`, `takeOps`, `flushNow` — the wire protocol carrying renders from BG to MT.
|
|
12
12
|
- **Main-thread refs** — `MainThreadRef`, `useMainThreadRef` — the BG-side handle whose `.current` value lives on the main thread; the build pipeline serializes these into worklet captures via their `_wvid`.
|
|
13
13
|
- **Cross-thread bridges** — `runOnMainThread` (BG→MT one-shot), `runOnBackground` (MT→BG dispatch handle), `transformToWorklet` (handle → JsFn marshal).
|
|
14
|
-
- **AnimatedValue BG sink** — `registerBgSink`, `unregisterBgSink`, `ingestAvPublishes` — receive MT-published `AnimatedValue` writes into a `signal`-backed mirror so `effect(() => av.value)` re-runs reactively. The producer side lives in [`@sigx/gestures`](
|
|
14
|
+
- **AnimatedValue BG sink** — `registerBgSink`, `unregisterBgSink`, `ingestAvPublishes` — receive MT-published `AnimatedValue` writes into a `signal`-backed mirror so `effect(() => av.value)` re-runs reactively. The producer side lives in [`@sigx/lynx-gestures`](https://github.com/signalxjs/lynx/tree/main/packages/lynx-gestures); the MT side lives in [`@sigx/lynx-runtime-main`](https://github.com/signalxjs/lynx/tree/main/packages/lynx-runtime-main).
|
|
15
15
|
- **JSX types** — `MainThread`, `Define`, `ViewAttributes`, etc.
|
|
16
16
|
|
|
17
17
|
## Wire protocol
|
|
18
18
|
|
|
19
|
-
Ops are flat-array tuples produced on BG and consumed on MT. The op codes (`CREATE`, `INSERT`, `SET_STYLE`, `SET_WORKLET_EVENT`, `INIT_MT_REF`, `REGISTER_AV_BRIDGE`, ...) are defined in [`@sigx/lynx-runtime-internal`](
|
|
19
|
+
Ops are flat-array tuples produced on BG and consumed on MT. The op codes (`CREATE`, `INSERT`, `SET_STYLE`, `SET_WORKLET_EVENT`, `INIT_MT_REF`, `REGISTER_AV_BRIDGE`, ...) are defined in [`@sigx/lynx-runtime-internal`](https://github.com/signalxjs/lynx/tree/main/packages/lynx-runtime-internal) so both sides stay in sync.
|
|
20
20
|
|
|
21
21
|
A typical batch:
|
|
22
22
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@sigx/lynx-runtime",
|
|
3
|
-
"version": "0.4.
|
|
3
|
+
"version": "0.4.4",
|
|
4
4
|
"description": "Lynx renderer for SignalX (background thread)",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "./dist/index.js",
|
|
@@ -41,7 +41,7 @@
|
|
|
41
41
|
"dependencies": {
|
|
42
42
|
"@sigx/runtime-core": "^0.4.8",
|
|
43
43
|
"@sigx/reactivity": "^0.4.8",
|
|
44
|
-
"@sigx/lynx-runtime-internal": "^0.4.
|
|
44
|
+
"@sigx/lynx-runtime-internal": "^0.4.4"
|
|
45
45
|
},
|
|
46
46
|
"peerDependencies": {
|
|
47
47
|
"@lynx-js/types": "*"
|