ploy vite

Use ploy vite for Ploy Vite projects, including React apps that ship a worker from worker/index.ts and TanStack Start apps.

Ploy reads ploy.yaml and drives the Vite toolchain from it, so all of your bindings, assets, and compatibility settings live in one place.

Commands

ploy vite build [options]
ploy vite dev [options]

Options

Any extra arguments are forwarded to the underlying Vite command.

When to use it

Use ploy vite when your project has both:

• a Vite config
• @meetploy/vite installed

For plain workers, use ploy dev / ploy build. For Next.js, use ploy dev with @meetploy/nextjs.

React + Worker Example

This setup matches examples/vite-full.

{
	"scripts": {
		"build": "tsc --noEmit && ploy vite build",
		"dev": "ploy vite dev",
		"types": "ploy types -o env.d.ts"
	}
}

kind: dynamic
build: pnpm build
out: dist
compatibility_date: "2026-03-23"
assets:
  binding: ASSETS
  not_found_handling: single-page-application
  run_worker_first:
    - /api/*
    - "!/api/docs/*"
db:
  DB: default

import { ploy } from "@meetploy/vite";
import react from "@vitejs/plugin-react";
import { defineConfig } from "vite";

export default defineConfig({
	plugins: [react(), ...ploy()],
});

For non-TanStack projects, Ploy looks for a worker entry at worker/index.ts or the corresponding JavaScript/MJS variants.

TanStack Start Example

This setup matches examples/tanstack-start-prerender.

{
	"scripts": {
		"build": "ploy vite build && tsc --noEmit",
		"types": "ploy types -o env.d.ts"
	}
}

kind: dynamic
build: pnpm build
out: dist
compatibility_date: "2026-03-17"
compatibility_flags:
  - nodejs_compat

import { ploy } from "@meetploy/vite";
import { tanstackStart } from "@tanstack/react-start/plugin/vite";
import viteReact from "@vitejs/plugin-react";
import { defineConfig } from "vite";

export default defineConfig({
	plugins: [
		...ploy({ viteEnvironment: { name: "ssr" } }),
		tanstackStart({
			prerender: {
				enabled: true,
				autoSubfolderIndex: true,
				crawlLinks: false,
				failOnError: true,
			},
		}),
		viteReact(),
	],
});

Assets

Use the top-level assets key in ploy.yaml to control static asset behavior for dynamic Vite deployments.

assets:
  binding: ASSETS
  not_found_handling: single-page-application
  run_worker_first:
    - /api/*
    - "!/api/docs/*"

• binding exposes the asset fetcher to your worker as env.ASSETS
• not_found_handling: single-page-application enables SPA fallback behavior
• run_worker_first lets API routes or other patterns bypass the asset layer

Local Development

pnpm ploy vite dev

This starts Vite dev mode with the config synthesized from ploy.yaml. If your app also uses Ploy bindings like db, generate types with ploy types first so env.d.ts stays current.

Build

pnpm ploy vite build

This runs the production Vite build using your ploy.yaml compatibility settings and asset config.

Notes

• Keep compatibility settings in ploy.yaml.
• Use assets in ploy.yaml to control static file behavior.
• If you need a custom Ploy config path, run ploy vite build --ploy-config path/to/ploy.yaml.
• If you need to pass Vite's own --config, forward it directly: ploy vite build -- --config vite.config.custom.ts.