@sveltejs/adapter-node

6.0.0 · 1 Oct 2026MIT1.2M / weekRepository Homepage npm Atom feed

Same major only

3 releases in betweenevery note read

Other targets from 5.5.5Newest 5.x5.5.7

9
changes to make: 0
advisories fixed: 3
new: 14
fixes

Before you upgrade

Tick each one off as you go

Populate env vars before instrumentation.server.js is evaluated and update the adapter instrumentation API
breaking6.0.0
Migrate from rollup to rolldown
breaking6.0.0
Require SvelteKit 3
breaking6.0.0
Add kit.paths.origin config option, remove kit.prerender.origin and the adapter-node ORIGIN environment variable
breaking6.0.0
Require vite@^8.0.12, the first Vite 8 release bundling stable rolldown 1.0.0
breaking6.0.0
Replace the builder.generateManifest with builder.generateServerInstance and builder.manifest
breaking6.0.0
Record the list of static assets at build time, files added to the output afterwards are not served
breaking6.0.0
Validate static assets with content-hash ETags and stop sending Last-Modified
breaking6.0.0
Serve static assets only to GET and HEAD requests
breaking6.0.0

Release by release

6.0.0
1 Oct 20263 new · 9 fixes
- new
  Serve static assets from tables recorded at adapt time, instead of using sirv
- new
  Better error logging
- new
  Abort request.signal when the response closes prematurely, via a new response option for getRequest
- fixed
  Prevent scheme-like path segments from causing off-site trailing-slash redirects
5.5.7
24 Jun 20262 fixes
- fixed
  Add X-Accel-Buffering: no header to text/event-stream responses to prevent reverse proxies such as nginx from buffering streamed responses
- fixed
  Delete existing socket file on startup
5.5.6
22 Jun 20263 fixes
- fixed
  Avoid circular dependency between server initialisation and hook retrieval that causes the app to crash on start
- fixed
  Correctly resolve root directory on the server
- fixed
  Ensure ENV_PREFIX is defined

11 internal lines (docs, tests, tooling) left out.

Upgrade to 6.0.0

npm install @sveltejs/adapter-node@6.0.0

What 6.0.0 needs

Reading 6.0.0's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 6.0.0. Read once, not stored.

After upgrading

Run the type checker, the linter and the tests.
Build, and look for new deprecation warnings.
Update peer dependencies the new version asks for.