Merge pull request #264 from solidjs/changeset-release/next

Version Packages (next)

Author: ryansolid

.changeset/pre.json

@@ -6,6 +6,8 @@
   },
   "changesets": [
     "empty-dragons-grow",
+    "lazy-manifest-robustness",
+    "native-compiler-option",
     "six-lions-joke",
     "true-boxes-arrive"
   ]

CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## 3.0.0-next.6
+
+### Minor Changes
+
+- 540f72e: Add an opt-in `compiler: "native"` JSX transform path powered by `@dom-expressions/jsx-compiler`.
+
+### Patch Changes
+
+- 5250437: Harden SSR asset resolution for `lazy()` modules.
+
+  - Every dynamically imported project module in SSR-mode client builds is now emitted as an explicit facade chunk (`preserveSignature: "exports-only"`), so it always gets a manifest entry keyed by its source path and a stable `default` export — even when `manualChunks` or dual static/dynamic imports would otherwise fold it facade-less into a shared chunk. This also covers `import.meta.glob` targets that never pass through the `lazy()` moduleUrl transform.
+  - Emitted facade chunks are reclassified from `isEntry` to `isDynamicEntry` in the virtual manifest so the runtime's entry-asset detection can't pick a lazy facade instead of the real client entry.
+  - SSR transforms now append a `$$moduleUrl` export carrying the module's client-manifest key. Server-side `lazy()` (solid-js ≥ 2.0.0-beta.17) reads it off the resolved module when the callsite has no static import specifier — enabling asset resolution and hydration preloading for glob-based lazy routes. Client builds are untouched.
+
 ## 3.0.0-next.5
 
 ### Patch Changes

package.json

@@ -1,6 +1,6 @@
 {
   "name": "vite-plugin-solid",
-  "version": "3.0.0-next.5",
+  "version": "3.0.0-next.6",
   "description": "solid-js integration plugin for vite 3/4/5/6/7",
   "type": "module",
   "files": [