René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Feature]: Promote `server` to Stable — freeze the `ctx`/`app` API and define exit criteria","articleBody":"**Pre-flight checklist**\n- [x] I searched existing issues and did not find a duplicate request.\n- [x] I explained the problem or use case, not just the desired API.\n\n**Problem or use case**\n`server` is **Experimental** and very young: it was introduced in 1.11.0, and a large slice of its request/response surface (`ctx.body`, `ctx.cookies`, `ctx.setCookie`, `ctx.accepts`, `ctx.stream`, `ctx.sse`, `ctx.renderStream`, `ctx.renderResponse`, and `app.listen()`) only landed in 1.14.0. A backend framework whose `ctx` shape changed materially one minor ago cannot be depended on for services. There is no published bar for what makes `server` stable.\n\n**Proposed solution**\nPublish exit criteria and freeze the `ctx` and `app` contracts for at least one minor cycle. Criteria: (a) frozen `ctx`/`app` surface with a documented request lifecycle; (b) test coverage across routing, streaming, SSE, cookies, and content negotiation; (c) the session/middleware primitives in #132 landed; (d) integration with file-based routing (#149) at least at the bridge level; (e) a documented per-runtime support matrix. Tracking issue for the `server` promotion.\n\n**Possible API or UX shape**\n```\n## Stability: targeting Stable in 1.15.0\nFrozen surface: createApp/app.use/app.route/app.listen, ctx.{req,res,params,\nquery,body,cookies,setCookie,accepts,stream,sse,renderStream,renderResponse}\nExit criteria:\n- [ ] ctx/app frozen for one minor\n- [ ] session + middleware primitives (#132)\n- [ ] file-based routing bridge (#149)\n- [ ] per-runtime support matrix (Node ≥ 24, Bun, Deno, edge)\n```\n\n**Alternatives considered**\nPositioning `server` as \"experimental, use Express/Hono in production\" — concedes the \"dependency-free backend\" differentiator that is one of the few things bQuery offers over client-only frameworks. Promoting without the session/middleware story (#132) — premature, since real services need both.\n\n**Relevant area**\n`server`\n\n**Additional context**\nbQuery's `server` is one of its genuine differentiators versus React/Vue/Svelte (which lean on separate backends), so stabilizing it is high-leverage. Must stay zero-dependency.\n","author":{"url":"https://github.com/JosunLP","@type":"Person","name":"JosunLP"},"datePublished":"2026-06-26T21:25:07.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/131/bQuery/issues/131"}