Supported frameworks and runtimes in Orbit
Supported frameworks and runtimes in Orbit
Orbit auto-detects your framework and applies the right build configuration automatically. No manual setup needed for supported frameworks.
Auto-detection
When you connect a repository, Orbit inspects your package.json and project structure to detect the framework. The detected framework is shown:
- As a badge on deployment cards in the project overview
- In the Framework field on the deployment detail page
If Orbit can't detect your framework, it falls back to running npm run build and serving the output directory.
Supported frameworks
| Framework | Auto-detected | Default build command | Default output |
|---|---|---|---|
| Next.js | ✅ | next build | .next |
| Vite | ✅ | vite build | dist |
| Create React App | ✅ | react-scripts build | build |
| Astro | ✅ | astro build | dist |
| SvelteKit | ✅ | vite build | build |
| Nuxt 3 | ✅ | nuxt build | .output |
| Remix | ✅ | remix build | build |
| Gatsby | ✅ | gatsby build | public |
| Static HTML | ✅ | (none) | root directory |
For server-rendered frameworks (Next.js with SSR, Nuxt, Remix), enable Server Mode in Settings to run your app as a Node.js process rather than serving static files.
Node.js version
Select your Node.js version from Settings → Build settings:
- Node.js 18 (LTS)
- Node.js 20 (LTS, recommended)
- Node.js 22 (Current)
The version applies to both the build environment and runtime (in server mode).
Package managers
Orbit detects and uses the right package manager automatically:
package-lock.json→ npmyarn.lock→ yarnpnpm-lock.yaml→ pnpm
Custom build settings
Override any auto-detected setting in Settings → Build settings:
| Field | Example |
|---|---|
| Build command | npm run build:prod |
| Install command | npm ci |
| Output directory | dist/client |
| Root directory | apps/frontend (monorepos) |
The Root directory field is useful for monorepos where your app lives in a subdirectory of the repository.
Build cache
Orbit caches node_modules between builds. When a cached install is used, the deployment detail shows a cache hit badge and the install step is much faster. To force a full reinstall, go to Settings → Clear build cache.