Compatibility
Find supported frameworks, commands, and package requirements.
Use Startpod to install dependencies, run development servers, and preview projects in the browser. Package compatibility depends on the Node.js APIs and operating-system features each dependency uses.
Supported paths
| Area | Current support |
|---|---|
| Project files | Text, binary files, directories, symlinks, watchers, import, and export. |
| Commands | Node.js entry files, npm scripts, npm install, npm init, npm exec and npx paths, local package binaries, and the bundled shell. |
| Development servers | Vite, Vite-based configurations, Next.js, and plain Node.js HTTP servers on tested versions. |
| Preview | Managed previews on separate runtime and preview app origins, or explicitly permitted same-origin previews. |
| Persistence | Project saves and optional install warm starts through IndexedDB. |
Test your product's real project
Compatibility depends on the packages, versions, scripts, and Node APIs a project uses. Before adding a template to your product:
- Pin the dependency versions.
- Run a clean install in Startpod.
- Exercise initial load, editing, hot updates, navigation, and server endpoints.
- Repeat the test against the built
startpodpackage rather than monorepo source.
See Limitations for the boundaries that are most likely to affect a product decision.