The Full Stack JavaScript SDK to build full stack apps and frameworks with your own opinions.
powered by vite and nitro
Compose full stack applications (and frameworks) using Vite, the versatile bundler and dev server, and Nitro, the universal production server. The core primitive in vinxi is a router.
Inspired by the Bun.App API.
- Routers are handlers that tell us how specific URLs should be handled. We support various router modes: "static", "spa", "http", (and new ones can be added). Routers specify the handler file (entrypoint) to use for their
base-prefixed routes. They can also specify adirandstylein some router modes to include a file system router that is provided to the handler. Routers specify their bundler configuration, via thebuildproperty. The routers tell the bundler what entry points to build, what vite plugins to use, etc.
| Framework | Category | Example | StackBlitz Link |
|---|---|---|---|
| React | RSC | SPA |  |
| SPA | Basic | |
|
| MDX | |
||
| TanStack Router (Pages) | |
||
| TanStack Router (App) | |
||
| Wouter | |
||
| SSR | Basic | |
|
| Basic w/Cloudflare | |
||
| TanStack Router (App) | |
||
| Wouter | |
||
| Solid | SPA | Basic | |
| SSR | Basic | |
|
| Solid Router | |
||
| Vanilla | SPA | |
|
| TRPC | |
Primary goal is to build the tools needed to build a NextJS or SolidStart style metaframework on top of vite without worrying about a lot of the wiring required to keep dev and prod working along with SSR, SPA, RSC, and all the other acronyms. etc. On top of that, we should be able to deploy anywhere easily.
Mostly trying to disappear for the user outside the app.js file
The surface layer we are intending to tackle:
- Full stack builds (handle manifest stuff to figure out what assets to load at prod runtime)
- Dev time asset handling (avoiding FOUC in SSR frameworks) and smoothing over some of vite's dev/prod mismatching behaviours by providing common manifest APIs that work in dev and prod the same way
- File system router (not any specific file system conventions, just an API for interfacing with FileSystemRouters and utils to implement your conventions in them)
- Building the server, and providing a simple opaque
handlerAPI to control the server - Adapter stuff to deploy to various platforms with support for all the features they provide
- Not to abstract away the platforms. Let people use what they want to the fullest
- Have little opinion about how the app should be authored or structured
-
vinxi deploy - hooks throughout the app licycle:
- dev: app:created, app:started, router:created
npm install vinxiimport reactRefresh from "@vitejs/plugin-react";
import { createApp } from "vinxi";
export default createApp({
routers: [
{
name: "public",
type: "static",
dir: "./public",
},
{
name: "client",
type: "client",
handler: "./app/client.tsx",
target: "browser",
plugins: () => [reactRefresh()],
base: "/_build",
},
{
name: "ssr",
type: "http",
handler: "./app/server.tsx",
target: "server",
},
],
});import { createApp } from "vinxi";
import solid from "vite-plugin-solid";
export default createApp({
routers: [
{
name: "public",
type: "static",
dir: "./public",
},
{
name: "client",
type: "client",
handler: "./app/client.tsx",
target: "browser",
plugins: () => [solid({ ssr: true })],
base: "/_build",
},
{
name: "ssr",
type: "http",
handler: "./app/server.tsx",
target: "server",
plugins: () => [solid({ ssr: true })],
},
],
});
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "github-actions[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent