What is this?
Nitro is a server toolkit that extends your Vite app with a production-ready server you can add routes to and deploy anywhere.
Nitro is a server toolkit that extends your Vite app with a production-ready server you can add routes to and deploy anywhere.Is this a standalone server or something I plug into my app?Nitro is not a standalone server app; it plugs into an existing Vite project and turns it into a deployable server by letting you add server routes on top of your app.
Nitro is not a standalone server app; it plugs into an existing Vite project and turns it into a deployable server by letting you add server routes on top of your app.How do I add Nitro to my project?You add Nitro into a Vite app and start defining server routes; the exact plugin setup and route API are covered in the official docs linked from the README.
You add Nitro into a Vite app and start defining server routes; the exact plugin setup and route API are covered in the official docs linked from the README.Do I need an existing Vite app and a specific Node version?Yes, Nitro is built to extend Vite apps, and it requires Node.js ^20.19.0 or >=22.12.0 according to the package engines field.
Yes, Nitro is built to extend Vite apps, and it requires Node.js ^20.19.0 or >=22.12.0 according to the package engines field.Is the current branch stable enough to use in production?The default branch is Nitro v3, which is still under active development; the README points users who need stability to Nitro v2 as the current stable release.
The default branch is Nitro v3, which is still under active development; the README points users who need stability to Nitro v2 as the current stable release.What does Nitro mean by 'zero-config' server experience?Nitro bundles core server pieces like HTTP handling (h3), routing (rou3) and caching (ocache) out of the box, so you get a working production server without wiring these pieces together yourself.
Nitro bundles core server pieces like HTTP handling (h3), routing (rou3) and caching (ocache) out of the box, so you get a working production server without wiring these pieces together yourself.Does Nitro support WebSockets?Yes, Nitro includes the crossws library as a dependency, giving it built-in cross-runtime WebSocket support alongside its HTTP server layer.
Yes, Nitro includes the crossws library as a dependency, giving it built-in cross-runtime WebSocket support alongside its HTTP server layer.Why does Nitro depend on packages like db0 and unenv?db0 gives Nitro a lightweight database connector and unenv provides environment polyfills, which together let the same Nitro server code run consistently across Node, edge and serverless runtimes.
db0 gives Nitro a lightweight database connector and unenv provides environment polyfills, which together let the same Nitro server code run consistently across Node, edge and serverless runtimes.Which topics is it in?edge, routing, logging, full-stack, hooks, serverless, caching, deployment, cloudflare, web-framework, vite, websocket
edge, routing, logging, full-stack, hooks, serverless, caching, deployment, cloudflare, web-framework, vite, websocket