@nuxt/vite-server

v4.6.2 is the next patch release.

Changelog

compare changes

Fixes

• nitro: apply useHeadSafe rules to server island head

• nitro-server: read router params from the path h3 matched

• nitro: match server route rules case-insensitively unless routing is sensitive

• nuxt: resolve rooted paths through the URL parser

• nuxt: resolve empty route types in shared context

• nitro: preserve server tsconfig with relocated build dir

• nuxt: fix scroll offset for IDs starting with numbers

• kit: do not exclude module directories with a dot in their name from app tsconfig

• nuxt: detect vapor slots with rawVaporSlotKey from vue

• nuxt: keep middleware layout when restoring deferred prerendered route

• schema: provide default value for experimental.typescriptPlugin

• vite: only replay compile error overlays to newly loaded pages

• nuxt: re-export AnyFetchPath for emitted server route types

• vite: warm up the dev ssr entry from a nitro plugin

• nitro: avoid unused h3 imports in nuxt/server runtime

• vite-server: scope asset url helpers to the build

• nuxt: resolve nuxt/app to the app's runtime

• kit: lowercase filename-derived handler method on nitro v2

• nuxt,nitro: normalise string/array appMiddleware

• nitro: pass response headers to render:response listeners

• vite: resolve inlined vue to its bundler build in dev

• nuxt: don't start a page transition with no page to leave

• nuxt: preserve error state on aborted or cancelled navigation

• vite,nitro: link null-byte virtual css through /@id/ in dev

• kit: resolve module dependencies from the declaring module

• nitro: only disable h3 + nitro presets when nitroAutoImports is off

• nitro,vite: don't access unspecified dependencies

• nitro: don't inline deps under absolute transpile dirs

• vite-server: respect spa loading template location

v4.6.1 is the next patch release.

Changelog

compare changes

Performance

• nitro: build the portable event's web view on first access

Fixes

• vite: match vite 8.1+ optimizer messages for deps hint

• nuxt: accept any baseURL when fetch response type is named

• nitro: resolve nitropack/types declarations under nodenext

• nuxt: allow false in setPageLayout types

• nuxt: align Serialize object types with JSON

• vite: don't abort dep scan on virtual imports in installed packages

• nuxt: update publishConfig config export extension

• kit: install the package a missing subpath belongs to

• vite-server: use the configured outDir as the public directory for non-ssr environment

• kit,nitro: match dev handler paths on both nitro majors

• nuxt: preserve onServerPrefetch for useId hydration

• vite-server: include the request in dev error reports

• nitro: register each dev server handler once

• nitro: pass RequestEvent to nuxt dev server handlers

• nuxt: type the global $fetch with nuxt's TypedFetch

• vite-server: work with deploy target plugins in dev

• schema: ignore .wrangler directory

• vite-server: pass the path to the error page render

• nuxt,vite: disable dev error broadcast if BroadcastChannel throws

• kit: align semantic version regexp with nightly version format

• nuxt: export types reachable from async data composables

• vite: detect enclosing string delimiter in inline style urls

• schema: type the nuxt dev server handler variant

• nitro: inline nuxt runtime when resolved to windows paths

• nitro: resolve unhead from nuxt in server bundle

Experimental: @nuxt/vite-server

Since v4.2 server.builder has been configurable. This release adds a second server builder: @nuxt/vite-server. It builds a Nuxt app with Vite alone (#36218, #36279, #36288).

This is all you need to do to configure it.

export default defineNuxtConfig({
  server: {
    builder: 'vite', // 'nitro' is the default
  },
})

It can produce a pure client SPA, a server-rendered app with a small Node entry, a web-standard fetch handler for platforms that provide the server (there are e2e examples for Cloudflare Workers, Netlify and universal deploy), as well as fully static output with nuxt generate.

Right now, this helps keep Nuxt's code agnostic, enforce the contract behind nuxt/server, and to give Vite plugins that provide a deploy target something to build on. It does not have Nitro's full feature set (there is no storage, caching, tasks or server plugins), and we expect most apps to keep using Nitro. Nitro remains the default.

[!WARNING]
This is highly experimental and the API will change. 'nitro' and 'vite' are new shorthands for @nuxt/nitro-server and @nuxt/vite-server.