Frameworks and platform limits
How Easel detects frameworks, what you can override, and current platform limits.
Easel detects your framework from the repository and sets build defaults automatically. You can override the framework preset, install command, build command, and output directory in Project settings.
Framework detection
When you import a repository, Easel inspects the project and suggests a framework preset. Common presets include Next.js, Remix, Vite, Nuxt, Svelte, Angular, Vue, React, Express, and Other.
Detection chooses build defaults. You remain responsible for an app that builds successfully with those settings. If detection is wrong, pick a different preset or set custom build commands.
What runs well today
Easel is built for modern JavaScript and TypeScript apps that produce a standard web output (static assets plus server routes where the framework supports them). Next.js is the best-supported path in templates and examples.
If your framework builds and the output matches what the selected preset expects, preview and production deploys work the same way as in Getting started.
On Next.js, revalidatePath and revalidateTag expire the shared tag clock and the edge CDN for that deployment. Any stack can set CDN TTLs and Cache-Tag on responses. Use Runtime Cache getCache() for framework-agnostic tagged key/value data. See Invalidate and revalidate cached content and Caching.
Build settings you can change
In project settings you can override:
- Framework preset
- Install command
- Build command
- Output directory
- Production branch (under Environments)
Environment-specific secrets live in Environment variables.
Platform limits (current)
Documented product limits today:
- Custom domains attach to production only. Previews use generated URLs. See Custom domains.
- Wildcard hostnames (
*.example.com) are not supported for custom domains. Add each hostname you need. - Environment targets are production, preview, and development. There is no separate staging target; use preview (or a preview branch override) for pre-production secrets.
- Public REST API and language SDKs are not available yet. Use the dashboard and CLI. See API reference.
Limits evolve with the platform. Prefer this page and the CDN / deployments guides over marketing posts when you need the current contract.
Related guides
- Getting started: first deploy from Git
- Runtime Cache: shared
getCache()across isolates - Easel CDN: caching, revalidation, headers, compression, and TLS
- Troubleshooting: common deploy and edge issues