Netlify Vite plugin Lets SolidStart 2 Deploy Without a Custom Adapter.

SolidStart 2 can now deploy full-stack applications to Netlify without a framework-specific adapter, a first for the deployment platform. Instead, the Netlify Vite plugin translates the server bundle produced by Vite into the configuration needed to run the application on Netlify.

The change is less about adding another supported framework and more about removing a longstanding integration burden. Framework authors and deployment platforms have traditionally maintained separate adapters for each pairing, creating a growing matrix of packages that must be updated whenever either side changes.

Netlify said in its LinkedIn announcement that supporting SolidStart 2 required no changes to its deployment pipeline. The same underlying approach has already powered TanStack Start deployments on Netlify for the past year.

SolidStart 1 used Nitro internally when deploying to Netlify. SolidStart 2 removes that dependency and instead builds directly on Vite’s Environment API, which gives frameworks a standard way to create builds for different runtime environments.

The Netlify Vite plugin consumes the server build emitted by Vite and prepares the required deployment configuration. Crucially, it does not need to know which framework generated that bundle. That abstraction means a compatible full-stack Vite framework can potentially use the same deployment path rather than waiting for a dedicated Netlify adapter.

According to Netlify’s official changelog, developers install the plugin as a development dependency:

npm install -D @netlify/vite-plugin

They then enable build support in vite.config.ts alongside the SolidStart plugin:

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 } })
  ]
});

Netlify detects SolidStart and supplies the build settings. Server-rendered pages, API routes, middleware and server functions are deployed through Netlify Functions. During local development, vite dev can emulate the Netlify platform inside the Vite development server, removing the need to launch the Netlify CLI separately.

Custom adapters often become hidden maintenance costs. Each one must track changes across a framework, its build tool and the target hosting platform. Less popular frameworks can consequently face delayed support, incomplete integrations or abandoned adapters.

A shared Vite-level integration changes that equation. Netlify can improve one deployment pipeline while framework teams build against Vite’s APIs. For small development teams, that could mean fewer packages to configure and fewer compatibility issues during framework upgrades.

The approach also leaves room for Nitro. Developers who prefer it can add the Nitro 3 Vite plugin, which automatically detects Netlify. In that configuration, Netlify advises removing build.enabled from its Vite plugin.

Existing SolidStart 1 projects do not have to migrate immediately. Their Nitro netlify preset remains supported. When upgrading, Netlify recommends following SolidStart’s migration guide, moving to the Vite plugin’s build support and changing the publish directory from dist to dist/client. Projects that continue building with Nitro can retain dist.

This release arrives as Netlify makes broader platform changes, including making new projects private by default. For builders evaluating SolidStart 2, however, the immediate benefit is narrower and practical: its full-stack features can deploy through a general-purpose Vite pipeline rather than a framework-specific bridge.

What is Netlify Vite plugin?

Netlify Vite plugin is a package that integrates Netlify’s platform with Vite development and build workflows. For SolidStart 2, it converts Vite’s server build into Netlify deployment configuration without requiring a dedicated SolidStart adapter.

How does SolidStart 2 deploy to Netlify?

Developers install @netlify/vite-plugin, add it to the Vite configuration and enable build support. Netlify then detects SolidStart and deploys SSR pages, API routes, middleware and server functions through Netlify Functions.

Do existing SolidStart 1 projects need to migrate immediately?

No. SolidStart 1 projects using the Nitro netlify preset will continue to work. Teams can move to the Netlify Vite plugin when they upgrade to SolidStart 2, or continue using Nitro 3 as a Vite plugin.