TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: Is building an MVP in Nestjs / TypeORM a mistake?

2 点作者 relaunched大约 4 年前

1 comment

emteycz大约 4 年前
If you haven&#x27;t yet, I urge you to try out TypeGraphQL, the development experience is just awesome. A demo can be running in 5 minutes[1]. TypeORM entity classes can be decorated with ObjectType&#x2F;Field, and having a single place for my DB as well as API schema is just perfect. A CRUD resolver base class can be reused by extension, and you can focus on specialized functionality instead of boilerplate.<p>[1] <a href="https:&#x2F;&#x2F;typegraphql.com&#x2F;docs&#x2F;installation.html" rel="nofollow">https:&#x2F;&#x2F;typegraphql.com&#x2F;docs&#x2F;installation.html</a><p>That said, I don&#x27;t think any choice of tech would be mistaken if it&#x27;s reasonably modern and alive.