What it does today:
- File-based routing (including dynamic and catch-all segments)
- API routes with consistent JSON error shape
- SSR by default, and `mode = "client"` per route when interactivity is needed
- Runtime module cache with file-change invalidation in local dev
Project goal: keep the runtime small and understandable so teams can iterate quickly and still reason about behavior.
I would really value feedback on:
1. Routing/API ergonomics
2. What was confusing or slow in your first 30 minutes using MicroVibe?
3. Where this should clearly differ from Next/Astro/Vite workflows
melendezgg•2h ago
MicroVibe is intentionally smaller than full frameworks. It currently optimizes for local iteration and explicit behavior over batteries-included features. If you need mature integrated ecosystems (auth adapters, image optimization, advanced build pipelines), bigger frameworks are still better defaults today. If this direction is useful, I’ll prioritize next:
- Official npm create onboarding flow
- Better starter templates
- More route/API examples and tests