When you create a new project on Esadax, our platform automatically detects the framework you're using and applies the optimal default settings. This ensures faster, more reliable deployments right from the start.
You can always override the default settings and manually select your framework from a comprehensive list of supported tools.
Why Framework Presets Matter
Framework presets provide:
- ✅ Preconfigured build commands, output directories, and install scripts
- ⚡️ Optimized deployment behavior for each framework
- 📦 Better support for framework-specific integrations and conventions
Popular Frameworks Supported
Esadax supports a wide variety of popular frontend and backend frameworks:
| Framework | Icon | Official Site |
|---|---|---|
| Next.js | https://nextjs.org | |
| Nuxt.js | https://nuxt.com | |
| Svelte / SvelteKit | https://kit.svelte.dev | |
| Vue.js | https://vuejs.org | |
| React (CRA) | https://reactjs.org | |
| Remix | https://remix.run | |
| Gatsby.js | https://www.gatsbyjs.com | |
| Hugo | https://gohugo.io | |
| Astro | https://astro.build | |
| Preact | https://preactjs.com | |
| Angular | https://angular.io | |
| SolidStart | https://start.solidjs.com | |
| Zola (Rust) | 🦀 Rust-based static site generator |
Other supported options include: Eleventy, Hexo, Jekyll, Hydrogen, RedwoodJS, Docusaurus (v1 & v2), and many more.
Manual Selection
If your framework isn't automatically detected, you can manually set it using the Framework Preset option in your project settings. This ensures:
- Correct build lifecycle commands
- Accurate output directory
- Framework-aware optimizations
Example Use Case
If you're using Next.js, Esadax will automatically configure:
Build Command:next buildOutput Directory:.nextInstall Command:npm installoryarn
If you're using something custom or an unsupported framework, select Other to define your own commands and directories.
Advanced Usage
You can customize further:
- Manually set Build Command
- Define a custom Output Directory
- Choose an Install Command
- Configure a Root Directory (for monorepos)
These settings help support custom setups like monorepos, hybrid backends, and microservices.
Learn More
For a full list of supported frameworks and configuration options, visit the Frameworks Documentation.
