solid-docs

What is this request related to? Request 📋 Suggested https://docs.solidjs.com/quick-start https://docs.solidjs.com/reference/rendering/render (no existing page covers this — that's the point of the request) 📋 General description or bullet points The gap There is currently nothing in the docs about rendering Solid anywhere other than the DOM. A search across for , , , , and returns zero hits in . So: "Can I build a mobile app with Solid?" — a very common first question — has no answer in the docs. () is a public, shipped Solid API with no reference page and no mention anywhere in the docs. Right now you have to read in the Solid repo to learn it exists. Prior art in neighbouring frameworks Both Svelte and Vue answer this in their own docs, and both did it recently: Svelte — FAQ entry on mobile apps: https://github.com/sveltejs/svelte/pull/18665 (merged) Vue — https://github.com/vuejs/docs/pull/3452 (open) Each covers two distinct paths: wrapping an SPA (Capacitor / Tauri) and rendering real native views through a custom renderer. Concrete proposal A short page under Guides (e.g. "Building for mobile"), or an FAQ entry if you'd rather introduce one, covering: 1. Wrapping a Solid SPA — Capacitor (there are official ) and Tauri. 2. Real native views via — lets Solid drive a non-DOM host. Worth a paragraph on its own merit, independent of any particular library, since the API is undocumented today. Optionally a follow-up reference page for under . Disclosure + offer I maintain Symbiote Native, which has a adapter () driving React Native's Fabric renderer with React out of the path, running on device. So I have an obvious interest here and I'm flagging it up front. I'm happy to write the PR, and equally happy for it to name no specific library at all — the missing coverage of and of the mobile question stands either way. One data point on how thin the current coverage is: the only mobile-related entry on solidjs.com's resources page, , is flagged in 's own data. 🖥️ Reproduction of code samples in StackBlitz _No response_

[x] I have read the Contribution guide [x] This PR references an issue (except for typos, broken links, or other minor problems) Description(required) Document that directly mutating an object or array stored in a signal does not notify subscribers because the setter is not called. The new example shows updating through the setter with a new array and points readers who need frequent nested updates to stores. Related issues & labels Closes #1621 Suggested label(s) (optional): documentation Verification Reviewed the MDX against the repository writing guide. Prettier dependency installation could not complete locally; CI will run in the repository-required Node 24 environment.

From solidjs/solid#3007 (reported by @mizulu). The reference page (https://v2.solidjs.com/reference/solid-js/reactivity/untrack) should document how interacts with async reads in 2.0: stops dependency tracking — reads inside it do not subscribe the surrounding computation. It does not opt out of async settlement. Reading an async source that is not yet ready inside still throws , which propagates to the owning computation: the owner suspends (participates in boundaries) and re-runs once the source first resolves. In other words, where is a pending async memo will still cause the owner to re-run when first settles — the read is untracked, but the not-ready suspension is part of async graph resolution, not tracking. The page should spell out this distinction (tracking vs. settlement) and show the pattern for a genuinely non-suspending read of a possibly-pending source (e.g. checking readiness with / as appropriate) so users aren't surprised that alone doesn't provide a fallback-value escape hatch. A fallback-value overload for was considered in solidjs/solid#3007 and rejected — the docs are the fix.