Choose a Watt 3 capability
Inspect configuration and dependencies before choosing a capability. Match specific frameworks before generic Vite: Nuxt, React Router, TanStack, Remix, and Astro can all include Vite configuration. Preserve existing framework build configuration.
| Framework | Capability | Guide |
|---|---|---|
| Next.js | @platformatic/next | Next.js |
| Nuxt | @platformatic/nuxt | Nuxt |
| Nitro | @platformatic/nitro | Nitro |
| React Router | @platformatic/react-router | React Router |
| TanStack Start | @platformatic/tanstack | TanStack |
| Vite | @platformatic/vite | Vite |
| Remix | @platformatic/remix | Remix |
| Astro | @platformatic/astro | Astro |
| Express | @platformatic/node | Express |
| Fastify | @platformatic/node or @platformatic/service | Fastify |
| Koa | @platformatic/node | Koa |
| NestJS | @platformatic/node | NestJS |
| PHP, WordPress, Laravel | External @platformatic/php | PHP |
Use major 3 packages for this release line and verify external capabilities separately.
Examples use module to identify the capability without hardcoding a stale schema URL.
If adding $schema, stamp it with the installed capability's version.
For a standalone capability, public server and orchestration options can be wrapped
under runtime. In a multi-app project, keep orchestration at the root and capability
configuration in each app directory. See integration.