vinxi: I needed a server
summary
vinxi claims to remove the repeated multi-server pain by combining bundling, dev server and runtime into one configurable tool. It is built on Vite and Nitro, exposes a bun app–like router API where each route can be static, API, client or SSR, and runs isolated Vite builds so you get isolated Vite routers with separate plugin pipelines and HMR for server and client. The demo shows file-system routing, API handlers and SSR all wired and running; goal is fewer adapters and predictable deployable outputs.
AI-written summary · about
chapters (9)
- 0:00Introduction and journey
- 1:43Lessons from Next.js
- 3:30Bliss.js and self-provisioning
- 5:12Building games and Vex
- 6:59Solid Start and deployment
- 8:26Challenges with adapters
- 9:50Next.js app directory and RSC
- 12:40Introducing vinxi
- 17:14Freedom in tooling
