DeepSeek, Qwen, Kimi and hundreds of open models now available.🎉

SolidStart 2 just works on Netlify

August 6, 2026

SolidStart 2 is out, and it deploys to Netlify with no framework-specific adapter to install, a first for full-stack frameworks on Netlify.

While SolidStart 1 deployed to Netlify through Nitro under the hood, SolidStart 2 no longer includes Nitro, building directly on Vite’s Environment API instead. The Netlify Vite plugin can now take the server build Vite produces and prepare it for deployment on its own, with no SolidStart-specific Netlify adapter needed in between.

How to deploy

Install the Netlify Vite plugin:

npm install -D @netlify/vite-plugin

Then add it to your Vite config with its build support turned on:

vite.config.ts
import netlify from '@netlify/vite-plugin';
import { solidStart } from '@solidjs/start/config';
import { defineConfig } from 'vite';


export default defineConfig({
  plugins: [solidStart(), netlify({ build: { enabled: true } })],
});

That’s the whole setup for a new project. Netlify detects SolidStart and fills in your build settings, and your SSR pages, API routes, server functions, and middleware deploy to Netlify Functions.

Prefer to build with Nitro? It became a Vite plugin in Nitro 3 and auto-detects Netlify, so adding nitro() works too. Just remove build.enabled from the Netlify Vite plugin.

Either way, vite dev gives you the full Netlify platform emulated right in your dev server without reaching for the Netlify CLI.

Already on SolidStart 1?

Nothing breaks, and your Nitro netlify preset keeps working. When you’re ready to upgrade, follow the framework upgrade guide. We recommend then moving to the Netlify Vite plugin with build support as described above and changing your publish directory from dist to dist/client. (If you keep building with Nitro, dist stays as it is.)

Why there’s no SolidStart adapter

Every framework used to need its own adapter for every platform, and every adapter needed someone to keep it current.

Frameworks converging on Vite’s Environment API doesn’t change this on its own. What removes it is the build support in @netlify/vite-plugin: it takes the server bundle a Vite-powered framework emits and turns it into Netlify deployment configuration (we call this the Frameworks API), without knowing or caring which framework produced it. Supporting SolidStart 2 required no SolidStart-specific code and, in fact, no changes at all. This is the same code that’s been powering TanStack Start on Netlify the past year.

It’s the direction we’re heading, in collaboration with the Vite team, framework authors, other platforms like Cloudflare, and the broader ecosystem: fewer adapters to maintain, more consistent feature sets across frameworks, and more niche frameworks supported out of the box, helping to support a healthy web ecosystem.

Resources