Version Packages (next)

[github-actions]

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

@solidjs/vite-plugin@3.0.0-next.49

Patch Changes

• be766d6: dev: false now serves Solid's production builds under vite dev, as documented (Disabling dev option does nothing #62). The plugin already dropped its own development condition, but Vite's default development|production condition resolves to development in any non-production mode, so the client still pre-bundled solid.dev.js / web.dev.js and SSR loaded server.dev.js. With dev: false the plugin now rewrites that condition to production under vite dev; vitest runs and vite build keep Vite's default resolution. Vite conditions apply per environment, so other packages that ship a development export also get their production builds in that case. It also stops emitting HMR refresh wrappers and pre-bundling solid-js/refresh, because the production refresh runtime is an inert stub that only warns; edits fall back to a full reload. The diagnostics bridge also stays off with dev: false unless observe is on, since its channels exist only in the dev and observe builds.
• af79dd8: Plain .ts and .js modules now get lazy callsite module URLs and, on the server, a $$moduleUrl export. Non-JSX files used to return before that pipeline, so a routes.ts of lazy(() => import(...)) never told SSR which module to preload.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@solidjs/vite-plugin@408

commit: 5455118