Solid 2.0 rc.13: runtime parity, call-record panel, observe exclusion

.changeset/rc12-call-record-observe.md

@@ -0,0 +1,9 @@
+---
+'@solidjs/start-devtools': patch
+---
+
+The server-function panel is driven by the runtime's `"call"` record.
+
+`observeServerFunctionCalls` was removed from `@solidjs/web/server-functions` in rc.9; the panel has shown nothing since. It now subscribes to `OBSERVE.records` for `"request"` and `"call"` with `bodies: true`: a call appears the moment its request is handed to `fetch` and completes when the caller's await settles, showing the request as sent and the response as it arrived, with unread bodies to inspect, the function's source name when the build carried one, and the call's timing. A call whose fetch itself failed is marked as failed, with the thrown value's message in place of the response.
+
+The toolbar excludes its own owner from the runtime's observe layer (`OBSERVE.exclude`) and hands the app it wraps back (`OBSERVE.include`), so the toolbar's own signals and effects are never reported as the app's by diagnostics, attribution, or the performance tracks.

.changeset/rc12-runtime-parity.md

@@ -0,0 +1,10 @@
+---
+'@solidjs/start-devtools': patch
+---
+
+Build and read the Solid 2.0.0-rc.12 runtime.
+
+The toolbar is compiled with `@solidjs/compiler`, the compiler that ships with the runtime, so delegated event handlers use the key the runtime reads (`_$$click`). Every click in the reactivity and ownership panels was dead against rc.9 and later.
+The `solid-js` and `@solidjs/web` peers move to `^2.0.0-rc.12`.
+The reactivity graph reads a node's error off its extension (`_x._error`), recognises store slot nodes by the store they belong to, and hides the memo the built-in hot reload wrapper creates, which the runtime now marks as plumbing instead of naming. The ownership tree walks through that memo without a row.
+A server render that fails sets the 500 status and logs, without writing toolbar state.

package.json

@@ -52,17 +52,17 @@
     "access": "public"
   },
   "peerDependencies": {
-    "@solidjs/web": "^2.0.0-rc.0",
-    "solid-js": "^2.0.0-rc.0"
+    "@solidjs/web": "^2.0.0-rc.13",
+    "solid-js": "^2.0.0-rc.13"
   },
   "devDependencies": {
     "@arethetypeswrong/cli": "^0.18.5",
     "@changesets/cli": "^2.30.0",
-    "@dom-expressions/compiler": "^0.50.0-next.43",
     "@jridgewell/trace-mapping": "^0.3.31",
     "@playwright/test": "^1.62.1",
-    "@solidjs/vite-plugin": "3.0.0-next.35",
-    "@solidjs/web": "^2.0.0-rc.0",
+    "@solidjs/compiler": "2.0.0-rc.13",
+    "@solidjs/vite-plugin": "3.0.0-next.46",
+    "@solidjs/web": "^2.0.0-rc.13",
     "@types/node": "^24.0.0",
     "error-stack-parser-es": "^2.0.1",
     "html-to-image": "^1.11.13",
@@ -72,7 +72,7 @@
     "rolldown-plugin-dts": "^0.28.2",
     "seroval": "^1.6.0",
     "shiki": "^4.3.1",
-    "solid-js": "^2.0.0-rc.0",
+    "solid-js": "^2.0.0-rc.13",
     "terracotta": "2.0.0-next.9",
     "typescript": "^7.0.2",
     "vite": "^8.2.1",

playwright.config.ts

@@ -1,5 +1,14 @@
 import { defineConfig } from '@playwright/test';
 
+// The toolbar only exists behind the `development` export condition, and the
+// runtime keeps render errors intact only in its development server build. The
+// worker processes running the server-side tests inherit this, so they resolve
+// solid-js and @solidjs/web the way a development server does.
+const conditions = '--conditions=development';
+if (!process.env.NODE_OPTIONS?.includes(conditions)) {
+  process.env.NODE_OPTIONS = [process.env.NODE_OPTIONS, conditions].filter(Boolean).join(' ');
+}
+
 export default defineConfig({
   testDir: './tests/e2e',
   reporter: process.env.CI ? 'github' : 'list',