@solidrt/core 0.0.53 → 0.0.54
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/AGENTS.md +10 -3
- package/package.json +2 -2
package/AGENTS.md
CHANGED
|
@@ -111,7 +111,12 @@ tsconfig.json - the two load-bearing lines are jsx + jsxImportSource:
|
|
|
111
111
|
```
|
|
112
112
|
|
|
113
113
|
Peer deps @solidjs/signals and @solidjs/universal must match (currently
|
|
114
|
-
2.0.0-rc.3); bun resolves them from peerDependencies.
|
|
114
|
+
2.0.0-rc.3); bun resolves them from peerDependencies. On a version bump,
|
|
115
|
+
`bun install` only warns ("incorrect peer dependency") and keeps the old
|
|
116
|
+
ones, and `bun update solid-js @solidjs/signals @solidjs/universal` does
|
|
117
|
+
not read the pin either: it adds all three to package.json at registry
|
|
118
|
+
latest (solid-js 1.x, off Solid 2.0 entirely). The recipe that works is
|
|
119
|
+
`rm -rf bun.lock node_modules/solid-js node_modules/@solidjs && bun install`.
|
|
115
120
|
|
|
116
121
|
## Element model (the parts that are easy to get wrong)
|
|
117
122
|
|
|
@@ -282,8 +287,10 @@ Peer deps @solidjs/signals and @solidjs/universal must match (currently
|
|
|
282
287
|
- Animation is target-shaped first: declare `transition` on the element and
|
|
283
288
|
write targets, and the runtime animates natively with no per-frame JS.
|
|
284
289
|
Reach for per-frame work only for genuinely procedural motion:
|
|
285
|
-
`onFrame((tick, frame) => {})` is the native hook (runtime-paced,
|
|
286
|
-
cleanup, auto-cleaned inside a reactive scope); `
|
|
290
|
+
`onFrame((tick, frame, rate) => {})` is the native hook (runtime-paced,
|
|
291
|
+
returns a cleanup, auto-cleaned inside a reactive scope); `rate` is the
|
|
292
|
+
display's nominal refresh rate in Hz, which a fixed-timestep loop needs
|
|
293
|
+
(see @solidrt/cli agents/debugging.md on stepping); `requestAnimationFrame`
|
|
287
294
|
exists as a web-standard one-shot but is not the preferred driver. A JS
|
|
288
295
|
tween loop or an animation library pushing interpolated values through
|
|
289
296
|
signals is the single most expensive mistake available here - read
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@solidrt/core",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.54",
|
|
4
4
|
"license": "MIT",
|
|
5
5
|
"funding": "https://github.com/sponsors/wellawaretech",
|
|
6
6
|
"author": "Antoine van Wel",
|
|
@@ -29,7 +29,7 @@
|
|
|
29
29
|
"AGENTS.md"
|
|
30
30
|
],
|
|
31
31
|
"devDependencies": {
|
|
32
|
-
"@solidrt/flux-types": "0.0.
|
|
32
|
+
"@solidrt/flux-types": "0.0.54"
|
|
33
33
|
},
|
|
34
34
|
"peerDependencies": {
|
|
35
35
|
"@solidjs/signals": "2.0.0-rc.3",
|