Vite SSR Boost plugin
A two-skill plugin that migrates a Vite and React Router SPA to SSR Boost or scaffolds a new SSR application.
- 119 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The skill rewrites project configuration, entries and scripts.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/vite-ssr-boostDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The skill rewrites project configuration, entries and scripts.
This is third-party code. Review the repository files before installing.
What it does
The Claude Code plugin carries two skills. `ssr-boost-migrate` moves an existing Vite and React Router 7 Data mode SPA to server rendering with `@lomray/vite-ssr-boost`. It records a baseline, checks version compatibility, runs a trial `init --dry-run`, applies changes and verifies streaming, hydration, bundle size and deployment readiness. `ssr-boost-new-app` scaffolds a new application from a template. The library itself adds SSR to a Vite project while keeping route objects and components. SSR and SPA output build from one app, and transport is a choice between a managed Express server and a Fetch handler. A migration usually touches five files: Vite config, HTML, client and server entries and `package.json` scripts.
Who it is for. Frontend teams on React Router 7 who want server rendering without moving to Framework mode.
Good fit when
- An SPA loses in search and its pages need server rendering.
- A migration must keep the app routes and providers.
- After migration, hydration and client bundle size are verified.
- A new SSR app is scaffolded from a template with one command.
Not a fit when
- The project runs on Next.js or another framework with built-in SSR.
- It uses `BrowserRouter` and the router cannot be rewritten.
- Vite and React versions are outside the supported ranges.
Example request
Migrate this SPA to SSR Boost: first `init --dry-run`, show the list of changes, then apply and verify hydration.Limitations
The skill targets Vite 6 or 7, React 18 or 19 and react-router 7 in Data mode. An app on JSX `BrowserRouter` must first move to `createBrowserRouter` with `RouterProvider`. Automatic init refuses ambiguous startup code, which you then edit manually from the reference. The testing kit and incremental SSR policy need a library release newer than stable 8.3.0. The marketplace install is derived from the manifest, while the project description documents only npm commands. The last commit dates from September 2026.
How to disable. Run `/plugin uninstall ssr-boost`. Project changes are reverted through git and the dependency is removed with `npm uninstall @lomray/vite-ssr-boost`.
FAQ
Which versions does the migration support?
The baseline is Vite 6 or 7, React and React DOM 18 or 19, and react-router 7 in Data mode.
How do I preview edits without applying them?
Run `npx ssr-boost init --dry-run`. The `--apply` flag makes the changes after review.
How do I create a new app?
With `npm create @lomray/ssr-app@latest my-app`; choose the `full` template with `-- --template full`.
What does `doctor` check?
The `npx ssr-boost doctor` command checks project setup after installation and migration.
How does SSR Boost differ from Framework mode?
It adds server rendering to an app in Data mode without rewriting it for Framework mode.
Discussion
No questions or reviews yet.
Related
PluginsA skill for the Vite SVG sprite plugin: setup, configuration, Vue and React components, SSR and migration from the old plugin.
A Vite plugin with an MCP server that shows the agent the components, routes and Pinia stores of a running Vue app
VibeStart composes a TypeScript project from chosen stack layers and gives the agent a verified base with rules and tests.
A Vite, Nuxt and Next.js plugin that exposes the state of a running Vue, React, Svelte or Solid app to an agent over MCP.
Nuxt MCP Dev
nuxt-mcp-dev / vite-plugin-mcp
A Nuxt module and a Vite plugin start an MCP server on the dev server port so the agent sees config, pages, components, auto-imports and the module graph
A Vite plugin with a skill that writes errors, requests and page snapshots to logs an agent reads to find the cause of a bug
README in short
The README divides the work into adding to an existing project and creating a new one. Links lead to the five-file migration guide and a route reference.