From 494dd5cfdb52136f2a415d204e2eddd0b207fd79 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Wed, 29 Jul 2026 17:51:41 +0000
Subject: [PATCH] Version Packages (next)

---
 .changeset/pre.json |  2 ++
 CHANGELOG.md        | 38 ++++++++++++++++++++++++++++++++++++++
 package.json        |  2 +-
 3 files changed, 41 insertions(+), 1 deletion(-)

diff --git a/.changeset/pre.json b/.changeset/pre.json
index f0d6b2e..83e12f3 100644
--- a/.changeset/pre.json
+++ b/.changeset/pre.json
@@ -15,9 +15,11 @@
     "client-manifest-outdir",
     "compiler-package-rename",
     "dev-css-and-client-manifest",
+    "dev-manifest-bridge-and-boundary-modules",
     "dev-ssr-entry-styles",
     "drop-vite-lt-6",
     "empty-dragons-grow",
+    "external-dev-styles",
     "host-integration-extension-points",
     "lazy-entry-eliminated-importers",
     "lazy-entry-rolldown-reclassify",
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 650bd1c..a703c11 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,43 @@
 # Changelog
 
+## 3.0.0-next.19
+
+### Patch Changes
+
+- 83f7bb5: Two pieces hoisted from SolidStart so any host gets them plugin-side:
+
+  - Dev-manifest HTTP bridge for isolated SSR runners. The dev asset resolver
+    lives in the Vite process and is normally reached through a
+    process-global registry; hosts that evaluate server modules in an
+    isolated module runner (nitro's dev worker, workerd via
+    @cloudflare/vite-plugin) can't see it, which broke lazy-route CSS and
+    hydration preloads in dev. With `ssr` enabled the dev server now serves
+    `GET /@vite-plugin-solid/dev-manifest?key=<module key>` (ResolvedAssets
+    JSON, `null` for unresolvable keys), and the dev flavor of
+    `virtual:solid-manifest` transparently falls back to fetching it when the
+    registry has no entry for the root — the endpoint URL is baked in at
+    module generation time from the live server's resolved origin, so
+    isolated runners need zero host code. In-process consumers still
+    short-circuit on the registry hit and never touch HTTP. Misses log loudly
+    on both sides (registry miss / empty resolution on the serve side,
+    non-OK responses and network failures on the fetch side) and resolve to
+    `null`, keeping the runtime's own no-assets warning as the final
+    catch-all.
+  - Always-on `server-only` / `client-only` boundary marker modules:
+    importing `server-only` from a module bundled for the client fails the
+    build with an error naming the importer (and vice versa for
+    `client-only`); the allowed environment resolves the marker to an empty
+    module. Ambient type declarations ship at
+    `vite-plugin-solid/boundary-modules`. The bare specifiers are claimed
+    even when React's same-named npm packages are installed; the errors are
+    prefixed `[vite-plugin-solid]`.
+
+- 8386fb4: Let provider-owned SSR environments serve turnkey development requests without
+  calling `ssrLoadModule`. Entry CSS and server functions are transported through
+  the generated handler so isolated runtimes retain SSR styles and HMR support.
+
+  Add `ssr.external` for integrations that also own the server build wiring.
+
 ## 3.0.0-next.18
 
 ### Patch Changes
diff --git a/package.json b/package.json
index da8f800..16d2435 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "vite-plugin-solid",
-  "version": "3.0.0-next.18",
+  "version": "3.0.0-next.19",
   "description": "solid-js integration plugin for vite 6/7/8",
   "type": "module",
   "files": [