Wyro – 在画布上绘制后端,导出无锁定的 TypeScript 代码

2作者: Paaul011 天前原帖
嗨,HN。Wyro 是一个可视化后端构建工具,可以编译成您完全拥有的普通 TypeScript 仓库。 <p>动机:AI 应用构建工具在生成应用方面表现出色,但在让您离开时却表现不佳。前端代码您总是可以提取出来,而后端则是人质——他们的运行时、数据库和部署目标。 <p>工作原理:您在画布上将模块(HTTP 路由、表、身份验证、队列、定时任务、多步骤管道)连接成一个图。这个图是中间表示(IR),编译器将其转换为一个传统的 Node 项目——类型化的 Express 处理程序、Drizzle 模式和迁移、基于表定义的 Zod 验证器,以及用于驱动的 `postgres`。运行时没有任何解释;图形不会被打包,它会被编译掉。 <p>我对它的测试标准:导出的 package.json 列出了 express、drizzle-orm、postgres、zod、dotenv 和 jsonwebtoken。没有我自己的包。删除您的 Wyro 账户,应用仍然可以运行。 <p>数据库的工作方式相同——连接您自己的 Supabase,资源配置发生在您的组织中,由您负责费用,通过管理 API 进行。我掌控画布,而不是您的基础设施。 <p>诚实的现状:这还是早期阶段,由我单独构建。生成的代码是我最有信心的部分,也是我最希望被拆解的部分。粗糙的边缘在周围的产品中,而不是编译器中。 <p>免费套餐,无需信用卡。您可以在五分钟内做的有用事情是导出一个项目,并在决定是否信任它之前查看可比较的代码。 <p>https://wyro.vercel.app <p>特别希望得到那些已经从托管构建工具迁移过来的人的反馈——哪些地方出现了问题,您希望导出中包含哪些内容。
查看原文
Hi HN. Wyro is a visual backend builder that compiles to a plain TypeScript repo you own outright.<p>The motivation: AI app builders got good at generating apps and stayed bad at letting you leave. Frontend code you can always lift out. The backend is the hostage — their runtime, their DB, their deploy target.<p>How it works: you wire blocks on a canvas (HTTP routes, tables, auth, queues, cron, multi-step pipelines) into a graph. That graph is an IR, and the compiler lowers it to a conventional Node project — typed Express handlers, Drizzle schema and migrations, Zod validators derived from the table definitions, `postgres` for the driver. Nothing is interpreted at runtime; the graph isn&#x27;t shipped, it&#x27;s compiled away.<p>The test I hold it to: the exported package.json lists express, drizzle-orm, postgres, zod, dotenv, jsonwebtoken. No package of mine. Delete your Wyro account and the app keeps running.<p>Databases work the same way — connect your own Supabase and provisioning happens in your org, on your bill, over the Management API. I hold the canvas, not your infrastructure.<p>Honest state of things: it&#x27;s early and solo-built. The generated code is the thing I&#x27;m most confident about and the thing I most want torn apart. Rough edges are in the surrounding product, not the compiler.<p>Free tier, no card. The useful thing you can do in five minutes is export a project and read the diff-able code before deciding whether you trust it.<p>https:&#x2F;&#x2F;wyro.vercel.app<p>Would especially like feedback from anyone who has migrated off a hosted builder — what broke, and what you wished the export had included.