Skip to content

Version Packages (next) - #264

Merged
ryansolid merged 1 commit into
nextfrom
changeset-release/next
Jul 10, 2026
Merged

Version Packages (next)#264
ryansolid merged 1 commit into
nextfrom
changeset-release/next

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

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 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.

@github-actions
github-actions Bot force-pushed the changeset-release/next branch from faf8293 to 3fde1a6 Compare July 9, 2026 04:24
@github-actions
github-actions Bot force-pushed the changeset-release/next branch from 3fde1a6 to 2e730a7 Compare July 10, 2026 21:47
@ryansolid
ryansolid merged commit 125ffab into next Jul 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant