Skip to content

Version Packages (next) #319

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
brenelz merged 1 commit into from
Aug 23, 2026
Merged

Version Packages (next) #319

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .changeset/pre.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,11 +26,13 @@
"compiler-package-rename",
"compiler-range-next-43",
"dev-asset-resolver-convergence",
"dev-boundaries-ssr",
"dev-css-and-client-manifest",
"dev-manifest-bridge-and-boundary-modules",
"dev-middleware-full-dispatch",
"dev-ssr-entry-styles",
"dev-toolbar-inspector",
"devtools-optional-peer-stub",
"drop-sc-bootstrap-head-splice",
"drop-vite-lt-6",
"empty-dragons-grow",
Expand Down Expand Up @@ -77,6 +79,7 @@
"turnkey-ssr",
"turnkey-start-option",
"virtual-manifest-types-subpath",
"vite-8-minimum",
"vite-9-environment-hooks",
"vite8-scan-jsx-classic",
"vitest-browser-mode-no-jsdom-default",
Expand Down
8 changes: 8 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,13 @@
# Changelog

## 3.0.0-next.32

### Patch Changes

- 2436bf5: Wire the Start development error boundary into server rendering and support direct `@solidjs/start-devtools` imports in apps with custom server and client entries.
- 473afd2: Start devtools are no longer enabled when `@solidjs/start-devtools` is not installed. Detection falls back to resolving the package from the plugin's own file (for pnpm-isolated installs where it is only a dependency of the plugin), but the package is declared an optional peer dependency of the plugin, so when it is absent Vite answers that resolution with its `__vite-optional-peer-dep:` stub instead of `null`. The plugin took the stub as a successful resolution, wrapped the generated client entry in `DevToolbar`, and the browser failed with `The requested module '/@id/__vite-optional-peer-dep:@solidjs/start-devtools:@solidjs/vite-plugin' does not provide an export named 'DevToolbar'`. The stub is now treated as "not installed".
- 791ae3e: Require Vite 8 or newer and remove the Vite 6 and 7 compatibility paths.

## 3.0.0-next.31

### Minor Changes
Expand Down
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@solidjs/vite-plugin",
"version": "3.0.0-next.31",
"version": "3.0.0-next.32",
"description": "solid-js integration plugin for Vite",
"type": "module",
"engines": {
Expand Down
Loading