Releases: solidjs/vite-plugin-solid
Releases · solidjs/vite-plugin-solid
Release list
vite-plugin-solid@3.0.0-next.7
Patch Changes
- f718828: Lazy-load the native JSX compiler so environments without native addon support can still use the default Babel compiler.
vite-plugin-solid@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 stabledefaultexport — even whenmanualChunksor dual static/dynamic imports would otherwise fold it facade-less into a shared chunk. This also coversimport.meta.globtargets that never pass through thelazy()moduleUrl transform. - Emitted facade chunks are reclassified from
isEntrytoisDynamicEntryin 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
$$moduleUrlexport carrying the module's client-manifest key. Server-sidelazy()(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.
- Every dynamically imported project module in SSR-mode client builds is now emitted as an explicit facade chunk (
vite-plugin-solid@3.0.0-next.5
vite-plugin-solid@2.11.12
Patch Changes
- 9e46d91: fix: preserve jsx for rolldown dep scan
vite-plugin-solid@3.0.0-next.4
vite-plugin-solid@3.0.0-next.3
vite-plugin-solid@2.11.11
Patch Changes
- 7f39675: Add vite 8 in peer deps
vite-plugin-solid@2.11.10
Patch Changes
- b19050a: Fix SSR resolve.external being unconditionally applied in Vite 6+
vite-plugin-solid@2.11.9
Patch Changes
- ce00b4b: Fix server-side testing with vitest/ssr