Skip to content

Releases

[email protected]

[email protected] Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Nov 19:39
8c34a50

Patch Changes

  • cdf4542: fix(web): only a server function call made inside an action gets the default revalidation (#4913)

    A non-GET call made while an action body runs (a core action, or a router formAction) is a mutation: it asks for single-flight collection, and its response reaches the flight consumers even with nothing folded, so a router revalidates every query. A call made anywhere else, such as a query's fetcher, no longer does, which stops the refetch loop that started in rc.22. Explicit X-Revalidate keys and redirects still reach the consumers wherever the call was made.

  • eb31c86: Fix the reactivity bugs in Milo's lean.test.ts repros (21 of 25; the other four stay pinned as open questions or as rulings not built yet):

    • Sync glitches: a stale CHECK no longer stops the next flush's marking (S0). A memo that reads its own child sees the updated value (S1). A queued child moves with its owner and no longer runs before the owner that disposes it (S3). Height adjustment no longer requeues an owner that reads its child (S2). A pass's owned write to a signal it just read is a missed wake (S4, F-10).
    • A tick that nets back to its starting value (D-8) no longer asks async readers a new question. A pass that read only committed values asks the committed question again, which is a quiet re-ask (F-9, K1/K1b). refresh() no longer launders a held new question (K4).
    • latest() keeps showing a held error, or a held first answer, while the next question is in flight (D-22, D-41; T2, K3).
    • A write lands while an <Errored> shows its fallback over a pending read (F-3, F-12; E1).
    • A hold's commit lands each async node on the answer to its own question, and a user effect waits for the end of the hold: a run owed for a superseded pass is dropped (F-1, F-2; T1).

    Size offsets: solid-js exports createRoot, createSignal and createRenderEffect as live bindings that enableHydration() reassigns, instead of wrappers that spread their arguments into the hydrated or core function. A client-only app calls the core function directly.

  • 0f6a978: seroval and seroval-plugins now depend on ^1.8.0 instead of the exact 1.7.0 pin, so apps can share one seroval copy with other packages on 1.8.

  • 93fa11a: fix: csstype is declared by the packages whose published JSX types import it (#4922). @solidjs/web (#4923) and @solidjs/h now depend on it, and solid-js, whose types no longer use it, drops it.

  • 6b317b2: @solidjs/web's published declarations no longer import heldRead from solid-js, which strips it from its own declarations. Any project with skipLibCheck: false got a type error from rc.22's client.d.ts. The seam now comes from solid-js/internal, which declares it. A new skipLibCheck: false type check over every @solidjs/web entry's published declarations catches a stripped import before release.

  • Updated dependencies [213c0af]

  • Updated dependencies [f2aba67]

  • Updated dependencies [cdf4542]

  • Updated dependencies [55f2f88]

  • Updated dependencies [6c7f186]

  • Updated dependencies [d9df504]

  • Updated dependencies [eb31c86]

  • Updated dependencies [02ed8fb]

  • Updated dependencies [2d7869d]

  • Updated dependencies [16353ab]

  • Updated dependencies [f57cc89]

  • Updated dependencies [6f4f693]

@solidjs/[email protected]

Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Nov 19:39
8c34a50

Patch Changes

  • cdf4542: fix(web): only a server function call made inside an action gets the default revalidation (#4913)

    A non-GET call made while an action body runs (a core action, or a router formAction) is a mutation: it asks for single-flight collection, and its response reaches the flight consumers even with nothing folded, so a router revalidates every query. A call made anywhere else, such as a query's fetcher, no longer does, which stops the refetch loop that started in rc.22. Explicit X-Revalidate keys and redirects still reach the consumers wherever the call was made.

  • 7302320: A server function called with one argument whose encoding has no bytes ('', an empty URLSearchParams, Blob, ArrayBuffer or Uint8Array) receives that value when the host passes the request on with no body, as Node adapters do for Content-Length: 0 (#4939). The format tag says one argument was sent, so the server decodes it from the empty body. Before, the call ran with no arguments: echo('') ran as echo(undefined). An untagged empty POST is still a zero-argument call.

  • 6c7f186: A reactive spread that evaluates to a falsy value ({...(cond() && { k: 1 })}) contributes no props, as {} does, on components and elements, on the client and the server (#4937). Since rc.9 it threw Cannot use 'in' operator … in false and halted reactivity: function sources were only checked for nullish values.

  • eb31c86: Fix the reactivity bugs in Milo's lean.test.ts repros (21 of 25; the other four stay pinned as open questions or as rulings not built yet):

    • Sync glitches: a stale CHECK no longer stops the next flush's marking (S0). A memo that reads its own child sees the updated value (S1). A queued child moves with its owner and no longer runs before the owner that disposes it (S3). Height adjustment no longer requeues an owner that reads its child (S2). A pass's owned write to a signal it just read is a missed wake (S4, F-10).
    • A tick that nets back to its starting value (D-8) no longer asks async readers a new question. A pass that read only committed values asks the committed question again, which is a quiet re-ask (F-9, K1/K1b). refresh() no longer launders a held new question (K4).
    • latest() keeps showing a held error, or a held first answer, while the next question is in flight (D-22, D-41; T2, K3).
    • A write lands while an <Errored> shows its fallback over a pending read (F-3, F-12; E1).
    • A hold's commit lands each async node on the answer to its own question, and a user effect waits for the end of the hold: a run owed for a superseded pass is dropped (F-1, F-2; T1).

    Size offsets: solid-js exports createRoot, createSignal and createRenderEffect as live bindings that enableHydration() reassigns, instead of wrappers that spread their arguments into the hydrated or core function. A client-only app calls the core function directly.

  • 0f6a978: seroval and seroval-plugins now depend on ^1.8.0 instead of the exact 1.7.0 pin, so apps can share one seroval copy with other packages on 1.8.

  • bed865a: An SSR document a shared cache may store (Cache-Control with public or s-maxage, or a storable CDN-Cache-Control) no longer tells the browser the request's trace: no <meta name="traceparent"> in the shell head and no trace entry in Server-Timing (#4938). The cache replays one response to every viewer, so each browser attached its spans to the request that filled the cache, and the per-request meta tag changed the body on every render, which defeated ETag revalidation. The decision reads the response head when the shell head is written, so an httpHeader("Cache-Control", …) set while the shell renders counts. Server-function reads already worked this way (#3985). getTraceContext() is unchanged.

  • 93fa11a: fix: csstype is declared by the packages whose published JSX types import it (#4922). @solidjs/web (#4923) and @solidjs/h now depend on it, and solid-js, whose types no longer use it, drops it.

  • 6b317b2: @solidjs/web's published declarations no longer import heldRead from solid-js, which strips it from its own declarations. Any project with skipLibCheck: false got a type error from rc.22's client.d.ts. The seam now comes from solid-js/internal, which declares it. A new skipLibCheck: false type check over every @solidjs/web entry's published declarations catches a stripped import before release.

  • Updated dependencies [cdf4542]

  • Updated dependencies [eb31c86]

  • Updated dependencies [0f6a978]

  • Updated dependencies [93fa11a]

  • Updated dependencies [6b317b2]

@solidjs/[email protected]

Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Nov 19:38
8c34a50

Patch Changes

@solidjs/[email protected]

Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Nov 19:39
8c34a50

Patch Changes

  • 213c0af: fix(signals): affects() on a derived store no longer marks the input stores whose proxies it holds (#4914)

  • f2aba67: Keep rows borrowed from another optimistic store connected to their source when the destination rebases a pending arrangement.

  • cdf4542: fix(web): only a server function call made inside an action gets the default revalidation (#4913)

    A non-GET call made while an action body runs (a core action, or a router formAction) is a mutation: it asks for single-flight collection, and its response reaches the flight consumers even with nothing folded, so a router revalidates every query. A call made anywhere else, such as a query's fetcher, no longer does, which stops the refetch loop that started in rc.22. Explicit X-Revalidate keys and redirects still reach the consumers wherever the call was made.

  • 55f2f88: fix(signals): an error boundary whose fallback was never on screen lets a pending retry through to the fresh loading boundary above it, instead of keeping a stale error (#4926)

  • 6c7f186: A reactive spread that evaluates to a falsy value ({...(cond() && { k: 1 })}) contributes no props, as {} does, on components and elements, on the client and the server (#4937). Since rc.9 it threw Cannot use 'in' operator … in false and halted reactivity: function sources were only checked for nullish values.

  • d9df504: An optimistic store's guess no longer answers a new question for a reader in another action's lane (#4929, F-6). After an archive action cleared the selection, selecting another card while a toggle's guess on the checklist store was still out remounted <Loading on={selected()}> with the store's "nothing selected" value (0/0 done) instead of its fallback: the region's readers read the archive's guessed cards store, so they ran in the archive's lane, and a lane reader was served the toggle's guess world. Such a reader now waits for the new question's answer, as a mainline reader of a target with no guess does.

  • eb31c86: Fix the reactivity bugs in Milo's lean.test.ts repros (21 of 25; the other four stay pinned as open questions or as rulings not built yet):

    • Sync glitches: a stale CHECK no longer stops the next flush's marking (S0). A memo that reads its own child sees the updated value (S1). A queued child moves with its owner and no longer runs before the owner that disposes it (S3). Height adjustment no longer requeues an owner that reads its child (S2). A pass's owned write to a signal it just read is a missed wake (S4, F-10).
    • A tick that nets back to its starting value (D-8) no longer asks async readers a new question. A pass that read only committed values asks the committed question again, which is a quiet re-ask (F-9, K1/K1b). refresh() no longer launders a held new question (K4).
    • latest() keeps showing a held error, or a held first answer, while the next question is in flight (D-22, D-41; T2, K3).
    • A write lands while an <Errored> shows its fallback over a pending read (F-3, F-12; E1).
    • A hold's commit lands each async node on the answer to its own question, and a user effect waits for the end of the hold: a run owed for a superseded pass is dropped (F-1, F-2; T1).

    Size offsets: solid-js exports createRoot, createSignal and createRenderEffect as live bindings that enableHydration() reassigns, instead of wrappers that spread their arguments into the hydrated or core function. A client-only app calls the core function directly.

  • 02ed8fb: A row moved into a keyed optimistic store before that store's first answer, then renamed there, shows the store's last answer once everything lands again (#4918, a regression from the #4907 fix). A returned answer was paired with a row lent by another store, which made that store's row stand in the slot, so later answers of this store went past it. A returned answer is reconciled against the rows on screen, which already include the lent row, so it now skips that pairing. A derive that writes its draft keeps it.

  • 2d7869d: fix(signals): a returned landing no longer reconciles its answer into a row another store lent, which made two keyed optimistic stores wait on each other and overflowed the stack in reasks() (#4928)

  • 16353ab: A keyed optimistic store whose derive returns its answer keeps a row's guess when the row leaves the answer and comes back while the guess's action is still out (#4907). A returned answer is reconciled by key against the rows on screen, and once an answer had dropped the row there was nothing to pair it with, so the row came back as a new row showing the server's value. A returned landing now pairs its new objects with the row targets first, the same way a derive that writes its draft already did.

  • f57cc89: <Loading on={key}> keeps its fallback when an action's optimistic guess re-derives content from a flight the key re-asked (#4927). Lane work served the flight's committed value keeps the node's pending (#4862). Two gaps let the fallback lift early and show the old key's content under the new heading:

    • A derived store's pass settled its property readers on its own, even though core kept the derive pending. The family now settles only when core does.
    • The served record was one global. A nested computation that ran inside the outer pass (a memo created or pulled mid-body) overwrote it, so the outer pass cleared its pending. The record is now kept per node.
  • 6f4f693: A declined guess reverts everywhere it is read while other actions are still out (#4932). A memo-fed heading over an optimistic store row kept showing a declined rename while the list beside it reverted: in one pass the heading read two holds (the re-asked list's and the rename's), and a reader was recorded only on the first hold it read, so the rename's landing never re-ran it. A reader is now re-run by every hold it read committed from.

@solidjs/[email protected]

Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Nov 19:39
8c34a50

Patch Changes

@solidjs/[email protected]

Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Nov 19:39
8c34a50

Patch Changes

  • 93fa11a: fix: csstype is declared by the packages whose published JSX types import it (#4922). @solidjs/web (#4923) and @solidjs/h now depend on it, and solid-js, whose types no longer use it, drops it.
  • Updated dependencies [cdf4542]
  • Updated dependencies [7302320]
  • Updated dependencies [6c7f186]
  • Updated dependencies [eb31c86]
  • Updated dependencies [0f6a978]
  • Updated dependencies [bed865a]
  • Updated dependencies [93fa11a]
  • Updated dependencies [6b317b2]

@solidjs/[email protected]

Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Nov 19:39
8c34a50

Patch Changes

@solidjs/[email protected]

Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Nov 19:39
8c34a50

Patch Changes

@solidjs/[email protected]

Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Nov 19:39
8c34a50

Patch Changes

  • ea8e37c: A production <Show> whose callback reads its value ({u => <p>{u()}</p>}) is lowered to a ternary only when when reads signals, memos, stores, names, literals and operators. A when that reads another object's member, such as a prop, keeps the component (#4936): the ternary wrote u() as a second read of when, and a prop's getter runs again on each read, so when={props.children} created the child twice and broke its hydration. JSX children without a callback still lower for any when.

@solidjs/[email protected]

Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Nov 19:39
8c34a50

Patch Changes

  • ea8e37c: A production <Show> whose callback reads its value ({u => <p>{u()}</p>}) is lowered to a ternary only when when reads signals, memos, stores, names, literals and operators. A when that reads another object's member, such as a prop, keeps the component (#4936): the ternary wrote u() as a second read of when, and a prop's getter runs again on each read, so when={props.children} created the child twice and broke its hydration. JSX children without a callback still lower for any when.