HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
wasp-lang
wasp
TypeScript2020–2025
wasp-lang / wasp

wasp

The batteries-included full-stack framework for the AI era. Develop JS/TS web apps (React, Node.js, and Prisma) using declarative code that abstracts away complex full-stack features like auth, background jobs, RPC, email sending, end-to-end type safety, single-command deployment, and more.

Web DevelopmentAI & Machine LearningSecurity & PrivacyDevOps & CloudCommunication & SocialAutomation & Workflows
Explore on GitHubRead Hacker News discussions
8Distinct people
37Mentions
1Explicit recommenders
18.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The batteries-included full-stack framework for the AI era. Develop JS/TS web apps (React, Node.js, and Prisma) using declarative code that abstracts away complex full-stack features like auth, background jobs, RPC, email sending, end-to-end type safety, single-command deployment, and more.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

Aider is one of my favorite AI agents, especially because it can work with existing codebases. We've seen a lot of good results from folks who used it with Wasp…

matijash used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 4:00:59 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year37 dated mentions

Observed mentions: 2020-02-22 18:15:52 UTC to 2025-07-20 21:10:37 UTC.

0369122020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 11 mentions; 1 submissions, 10 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 10 mentions; 2 submissions, 8 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC11110
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC1028
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC413
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC514
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC312

What Hacker News says

11 sources
matijash·Mar 4, 2020
As some already mentioned below, in my opinion it would depend on the purpose of the language. In the case of the general language, these are some of my personal favourites: - expressive type system - easy & intuitive to start with, but also powerful if needed (low floor, high ceiling) - has a relatively small set of core concepts which are then composed together to build things further - rich set of libraries (although pretty obvious and not really a feature) I think our search for the "grail" general language will continue, probably forever. Languages such as Haskell, Rust & Go (and probably a lot of others I haven't heard of) are breaking the boundaries and introducing new concepts which then slowly spill over to more "mainstream" languages (e.g. the advent of functional programming constructs we are witnessing in Java, JS etc.). Other
Read the rest
than that, I also believe that more and more DSLs will start appearing, which is basically languages specialised for a specific purpose - which will make them extra convenient in their domain but not usable in the general case. Also, I expect the tooling (IDEs, build systems) to become more tightly integrated with the language, especially for the DSLs - creating the end product which at the end will be usable not only by the programming experts. I have actually, together with my brother, been working on such an idea for the past year. We made a DSL for the domain of web apps - it is basically a declarative language that compiles to the stack of choice implemented in the general language (e.g. React/Node). This makes it possible to express some web-app specific concepts with much less code, but is also constrained to that specific domain. If anybody wants to take a look it is here: https://github.com/wasp-lang/wasp Would be interesting to see the results of your research and what majority thinks are the ideal language features.
In Ask HN: What features would your ideal programming language have?
matijash·Mar 4, 2020
As many others below, I can also say I sympathise and often feel the same. As you said, everything feels super fragile and held together with only duct tape. Why is it so? I believe because everything started switching to web lately so it gained a lot of focus. Being open-source in nature it attracted a lot of new ideas and this is what lead us to the influx of new frameworks we have today. It is a good thing because innovation->improvement, but also a bad thing because a huge mess and choice paralysis :D. I also feel overwhelmed with all the transpiler and compilation steps, pretty much gave up on understanding everything. How to hate it less? What @valand suggested below makes sense to me, by focusing less on the technology and its brokeness, but rather on the product, best practices and the end-goal. Also, even if the build system is a
Read the rest
mess we can still write clean, high-quality and tested code which can be reused. This is what we did, propagated this culture through the team and that helped me hate things less. We were reading engineering books, having clean code dojos, best practice presentations etc. My takeaway from that was choose your victories when you can have them and enjoy them. Another approach would be to join the madness by creating your own solution - which is what I also did. I know it is a https://xkcd.com/927/ case, but it was too fun and interesting so I couldn't help it :) We basically built a DSL that compiles to the underlying stack of choice. If somebody wants to give it a look it is here: https://github.com/wasp-lang/wasp Good luck and hope you find peace with whatever you choose!
In Ask HN: Help me like modern web development
matijash·Feb 28, 2020
I like the demos a lot, it is easy to understand the idea from them! How hard was it to write the browser extension and how well does it work for the different sites? Obviously the main challenge, as other mentioned, is that not all of the data is present on the frontend. Also, user cannot permanently change the app, since just the DOM is changed and that is not persisted anywhere, am I right? But the whole idea to be able to peek "under the hood" of an app and customise/edit it sounds very appealing to me! I am actually working on the open source project that has that aim, to "understand" the web app from within. But of course for that we had to go with a bottom-up approach, so we are building a DSL for describing how a web app behaves: https://github.com/wasp-lang/wasp Would be happy to hear your thoughts on it!
In Wildcard: Spreadsheet-Driven Customization of Web Applications
matijash·Feb 25, 2020
I believe there will always be place for coding, even for HTML/CSS. The more common problems that are recognised as "patterns" are going to be handled by the specialised tools (such as Webflow which you mentioned), but there is always going to be the next level of complexity which has not been tamed yet. This is how I see the innovation cycle: New tech that makes X easier comes out. People use it and do things they couldn't do before - but then the patterns emerge, people often do Y but since this tech is general it takes a lot of work to achieve it. Then the new product comes which makes Y easier. HTML and CSS (especially advanced preprocessors such as Sass /Less) will always be more expressive than some visual tool, and some things will be really hard/clumsy without them. Of course, the question is in what volume will such "harder" prob
Read the rest
lems be there in the future. What to learn? HTML/CSS/JS are still very much used, but more and more within the different frameworks/tools. So maybe it wouldn't be bad to learn e.g. React. Just focusing solely on the HTML or CSS itself, I am not sure how beneficial is it to have e.g. 80% mastery vs 99% mastery. What kind of projects would require and adequately appreciate such knowledge? Btw, I am working on an open-source low-code solution - as opposed to Webflow and others, we still very much rely on the code, just try to abstract away the common patterns and let developer focus on the unique product logic. In our vision of the future the coding is going to stay, it will just become more and more integrated within the tools which will take away the "setup" complexity. So more and more people will be able participate in the development, even coding, while having the "safety net" of the underlying tool. This is our repo, would be happy to get your feedback! https://github.com/wasp-lang/wasp
In Ask HN: Low Code tools like Webflow, what's my role in the future?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.