Skip to content

RFC tracking: using any Solid package from .rx, in 35 small proposals #37

Open

Description

@yumemi-thomas

Branch claude/magical-bell-pfhb1w adds about 60 commits on top of upstream main so that .rx can use real Solid 2 packages (@solidjs/router 2.0, TanStack Router, Start and Query, Kobalte, Formisch, @solid-primitives, TanStack Virtual) and get the checker's guarantees across the JS boundary. This issue splits that work into small RFCs, one per idea, ordered so that each depends only on earlier ones (or on upstream PR solidjs#69, which this branch builds on).

Each RFC has a summary, motivation, proposal, drawbacks and alternatives, and the commits, spec rules, scenarios and tests that implement it. Some have open questions.

Declaring JS in .d.rx

RFC Issue Depends on
01 TypeScript-shaped signatures in .d.rx #2 —
02 One rule for where every .d.rx word goes #3 01
03 Pinning a declaration to a package version #4 —
04 Where a package's declaration is found (rx-types/, package, @rx-types, generated) #5 03
05 JS contexts: export context, uses(c), provides(c) #6 —
06 Fields of a JS result that wait or fail #7 02
07 Explicit handler callbacks in JS declarations #8 —
08 tracked callbacks #9 02, 07
09 A library's drafts: draft callback parameters #10 01, 07
10 Signal parameters: signal init: T #11 01

Language surface

RFC Issue Depends on
11 Typed closure parameters and type arguments at a call #12 —
12 Imports for their effect (import "./app.css") #13 —
13 ref on an element is a handler #14 07
14 Values that never change need no peek #15 —

Components and routes

RFC Issue Depends on
15 Exporting a factory's component #16 01
16 Route tables: defineRoute inside a factory, and layout routes #17 15
17 renders and renders(root, ctx…) #18 05
18 Components that travel in values: renders(later), nests(… under …), outlet, one placement vocabulary #19 05, 16, 17
19 The cautious placement #20 17
20 Render props: {view (row, i) { … }} #21 —
21 Compound components: <Dialog.Trigger> #22 01, 05
22 Typed route params and search params #23 01, 16

Types and tooling

RFC Issue Depends on
23 Types across the boundary #24 04
24 Checking a .d.rx against its module's real types #25 23
25 Type-checking in the production build #26 23
26 rx-declare: drafting a .d.rx from a package #27 01, 05
27 Generated declarations #28 04, 19, 26
28 rx-verify: checking a declaration by running its module #29 05, 06, 07
29 Strict declarations #30 28

Interop and SSR

RFC Issue Depends on
30 SSR: the app takes its request #31 —
31 .rx components for a JS host (?rx-lib, TanStack Start) #32 23, 30
32 SSR: a declared JS error class crosses as itself #33 30
33 Warn when the server renders with two copies of @solidjs/web #34 —

Checks

RFC Issue Depends on
34 SNAPSHOT_KEPT: refuse a kept peek of what changes #35 —
35 Whole-program checking for SNAPSHOT_KEPT #36 34

Not proposed as RFCs

These changes on the branch are fixes or test support, not language proposals:

  • the Solid pin (now upstream's 2.0.3 for ref/) and the setup-script and prelude-escape fixes;
  • the example apps and their Vite, SSR, Start, Kobalte and Formisch suites;
  • the -- spa, -- whole-program and -- accept: whole-program blocks in scenarios, and the ref/crate.ts parity modes;
  • the client-only first-load check in ref/ (CN-3d) for parity with the crate;
  • the diagnostics guide's tested before/after examples.

Not ours: upstream PR solidjs#69 (applying Solid components and router factories from .rx), which this branch merges and builds on.

Second review (2026-11-21, cdc00d4)

Revisions from the second, independent review, each noted on its RFC: 03, 04, 06, 07, 08, 09, 11, 14, 16, 17, 18, 24, 25, 27, 28, 29, 32, 33, 34, 35. New diagnostics: DRAFT_ESCAPES (MO-10i), RENDERS_ESCAPES (MO-11l, MO-11o). New row word: methods(…) (E-10, MO-8i). rx-verify records carry version: 2; older records need a rerun under strict mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions