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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Show HN: Wasp – DSL/framework for building full-stack web apps – now in beta

115 点作者 matijash超过 2 年前
Hey HN! Wasp (<a href="https:&#x2F;&#x2F;wasp-lang.dev&#x2F;" rel="nofollow">https:&#x2F;&#x2F;wasp-lang.dev&#x2F;</a>) is a simple config language (DSL) and framework for building full-stack web apps. You describe the high-level features you want (auth, CRUD, async jobs, …) using the Wasp DSL, and write the rest of your logic in React, Node.js, and Prisma. We’re focused on simplifying developer experience and ensuring best practices. Everything is open source.<p>Why another full-stack framework? And why a config language&#x2F;DSL? We were still experiencing a lot of boilerplate (repetitive tasks) using other frameworks—things like duplicating data models across database&#x2F;server&#x2F;client, implementing CRUD API, setting up auth, and choosing and stitching together all parts of the stack.<p>There are two main reasons for the DSL approach - 1) short-term: simpler and cleaner DX via a declarative language that helps avoid boilerplate, and 2) longer-tem: laying foundation for the stack &amp; architecture independent system.<p>Since Wasp analyses the app’s requirements in compile time, it can decide how to generate the target code (React &amp; Node.js currently). In the future it could support other stacks such as e.g. Vue&#x2F;Svelte on the client and Python&#x2F;Go on the server, even allowing for mixing’n’matching. The same goes for the architecture (dedicated server, serverless, …).<p>Our big vision for Wasp is to become a stable, stack-agnostic language for describing (web) app requirements (like SQL for databases or Terraform for infra) that interops with the existing stack. Wasp-lang stands for “Web Application SPecification language”.<p>Besides the DSL, another valid approach would be to offer an SDK in e.g. JS or Python to build Wasp AST (like Terraform and Pulumi now both offer). We see it as another “frontend” for constructing the AST and might also introduce it in the future.<p>Under the hood, everything is compiled to a client (React) and server (Node.js&#x2F;Prisma) apps and we generate static files and a Docker image you can use for deploying to your platform of choice.<p>Wasp had an Alpha launch 1.5 years ago (<a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=26091956" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=26091956</a>). Now we are more stable and feature-full. We still expect things to change, so wouldn’t recommend using Wasp for heavy production or mission-critical systems just yet. But it has been used for hackathons, internal tools and even revenue-generating products (<a href="https:&#x2F;&#x2F;wasp-lang.dev&#x2F;blog&#x2F;2022&#x2F;11&#x2F;26&#x2F;erlis-amicus-usecase" rel="nofollow">https:&#x2F;&#x2F;wasp-lang.dev&#x2F;blog&#x2F;2022&#x2F;11&#x2F;26&#x2F;erlis-amicus-usecase</a>).<p>The current release is our biggest since we launched (<a href="https:&#x2F;&#x2F;wasp-lang.dev&#x2F;blog&#x2F;2022&#x2F;11&#x2F;29&#x2F;wasp-beta" rel="nofollow">https:&#x2F;&#x2F;wasp-lang.dev&#x2F;blog&#x2F;2022&#x2F;11&#x2F;29&#x2F;wasp-beta</a>). Besides general stability and DX improvements, it brings support for TypeScript (<a href="https:&#x2F;&#x2F;wasp-lang.dev&#x2F;blog&#x2F;2022&#x2F;11&#x2F;29&#x2F;typescript-feature-announcement" rel="nofollow">https:&#x2F;&#x2F;wasp-lang.dev&#x2F;blog&#x2F;2022&#x2F;11&#x2F;29&#x2F;typescript-feature-ann...</a>), Tailwind (<a href="https:&#x2F;&#x2F;wasp-lang.dev&#x2F;blog&#x2F;2022&#x2F;11&#x2F;16&#x2F;tailwind-feature-announcement" rel="nofollow">https:&#x2F;&#x2F;wasp-lang.dev&#x2F;blog&#x2F;2022&#x2F;11&#x2F;16&#x2F;tailwind-feature-annou...</a>), async jobs via pg-boss (<a href="https:&#x2F;&#x2F;wasp-lang.dev&#x2F;blog&#x2F;2022&#x2F;06&#x2F;15&#x2F;jobs-feature-announcement" rel="nofollow">https:&#x2F;&#x2F;wasp-lang.dev&#x2F;blog&#x2F;2022&#x2F;06&#x2F;15&#x2F;jobs-feature-announcem...</a>), full-stack authentication (now also with Google) (<a href="http:&#x2F;&#x2F;localhost:3000&#x2F;blog&#x2F;2022&#x2F;11&#x2F;15&#x2F;auth-feature-announcement" rel="nofollow">http:&#x2F;&#x2F;localhost:3000&#x2F;blog&#x2F;2022&#x2F;11&#x2F;15&#x2F;auth-feature-announcem...</a>), and by popular demand, Wasp LSP with VS Code integration (<a href="https:&#x2F;&#x2F;wasp-lang.dev&#x2F;blog&#x2F;2022&#x2F;12&#x2F;01&#x2F;beta-ide-improvements" rel="nofollow">https:&#x2F;&#x2F;wasp-lang.dev&#x2F;blog&#x2F;2022&#x2F;12&#x2F;01&#x2F;beta-ide-improvements</a>).<p>Our next focus will be on making Wasp even easier to use (examples, starter templates, UI helpers), and we’ll look into tighter weaving of data models with the rest of the stack and expanding the DSL with more functionalities.<p>We’re around to answer questions and look forward to hearing everything and anything you have to say!

12 条评论

kinos超过 2 年前
The only thing preventing me from jumping right onto this is the fact it doesn&#x27;t seem to be an oauth2 provider, and it doesn&#x27;t seem to have the verify&#x2F;reset&#x2F;etc jobs necessary for username &amp; password.<p>Verify&#x2F;reset&#x2F;etc is always what pushes me away from doing multi-user webapps. Its a headache every time due to needing to think about e-mail, and I&#x27;d love an all-in-one oauth2 provider with signup and etc thats super lightweight and just does everything through an API.
评论 #33914957 未加载
dom96超过 2 年前
Congrats on this new milestone! I had a lot of fun completing some Hacktoberfest tasks back in October for Wasp, it was a lovely experience.<p>What&#x27;s most interesting (to me at least, as someone that loves building and learning about new languages) is that Wasp is YC funded. Probably the first language project I have seen to be part of YC.
评论 #33911671 未加载
desireco42超过 2 年前
Wow, wonderful of you to make this. It really causes a lot of burnout to make things over and over.<p>I will need to play with this to make more informed opinion, but based on description and info on landing page, I love what you are doing.<p>One thing that crosses my mind, clearly not applicable in this case as you are far along, but making it more interesting to write these specs would go a long way on improving how people use this. Like, I would consider some kind of markdown or at least TOML... something with indentation as opposed to braces.<p>Anyhow, anything that would save me from writing boilerplate code is more then welcome.<p>It would be cool if there is a standard way and then people start making plugins and stuff. It would have to be open source as VCs spoil the thing.
评论 #33911389 未加载
评论 #33911411 未加载
aatd86超过 2 年前
Interesting! When did you join YC? At what stage of the development of the language were you then?
评论 #33912978 未加载
dotneter超过 2 年前
Is it possible to use Wasp without framework as just a language, similar to something like Smithy?<p>For example I could describe my application with Wasp, write some code generator and generate my own code with it?<p>Would it make any sense to use it like this?
评论 #33921621 未加载
0xferruccio超过 2 年前
This looks slick! Have you thought about helping people structure in a more opinionated way how business logic gets run?<p>It feels like the JS ecosystem is missing framework that helped define layers of an app much like Rails&#x2F;Django
评论 #33914337 未加载
评论 #33914389 未加载
jstummbillig超过 2 年前
Hey, that&#x27;s cool. Are there any plans to help with bridging the gap to native or do you consider that outside the scope of what Wasp is concerned with?
评论 #33912097 未加载
brushfoot超过 2 年前
Help me understand the selling point of Wasp versus Next. The Wasp homepage says:<p>&gt; How is Wasp different from Next.js &#x2F; Nuxt.js &#x2F; Gatsby?<p>&gt; TL;DR - These are frontend-first frameworks, with some limited backend capabilities.<p>&gt; [...]<p>&gt; Although some of them now offer an option to use serverless functions, you still have to bring your own database and you&#x27;ll also need some kind of a server&#x2F;backend if you&#x27;ll need to run more complex operations.<p>That&#x27;s a big understatement; Next is fully full stack. You get API endpoints and server-side rendering out of the box.<p>You can deploy the backend as serverless functions, yes, but you can also deploy it as a plain old Node app.<p>Does Wasp offer something on the backend that Next doesn&#x27;t?<p>&gt; you still have to bring your own database<p>Confused on this one - does Wasp abstract away the database? The docs show a database connection config and mention using Prisma as the ORM. It looks similar to what I&#x27;d do in Next.
评论 #33919529 未加载
cpursley超过 2 年前
Any plans for other backends like Hasura or Supabase?
评论 #33913031 未加载
abraxas超过 2 年前
If I&#x27;m writing React and Prisma code here... what exactly does Wasp solve? Can someone explain this to a relative web stuff layman?
评论 #33919031 未加载
评论 #33919701 未加载
thih9超过 2 年前
This looks really cool, congrats on the launch! Do you have any plans to monetise it? If so, how?
评论 #33915291 未加载
ilrwbwrkhv超过 2 年前
Do you have an uninstall script?
评论 #33921029 未加载