Subscribe
Sign in
Wasp-lang (Beta) — Develop web apps in React & Node.js with no boilerplate
Wasp is the fastest way to develop full-stack web apps in React & Node.js. Describe high-level features (auth, CRUD, async jobs, …) via a simple config language, and write the rest of your logic in React, Node.js and Prisma.
110
Replies
@vedranrasic Thanks so much Vedran! Definitely let us know if any questions, always happy to help
Amazing product by an amazing team! Well done & great launch! I can't wait to see where you take this next.
I love what Beta looks like and it's amazing to see all these new features! Wasp really looks like something that could make developers' lives a lot easier. Exciting times!
Great work @martin_sosic & @matijash and the rest of the team!! 🙌💪 Great to see all the improvements you added! Keep up the awesome work 🍻
Can't wait to see 🐝 🚀 🌙
Wow, this looks like something new. I’ve always wanted to develop my own side projects, but it was always so hard to get started. What are the deployment options, how much does Wasp cover here?
@hassankhosseini Thanks :)!
For now Wasp spits out Dockerfile for you, for backend, and static page for frontend, and we have detailed instructions on how to deploy this to Heroku/Fly/Railway. But, you could take it and deploy where you want. For now this works pretty well, but the next step would be to make this more mainstreamed by having Wasp do some/all of the setup for you, for supported hosting providers!
Wow Beta is here! Really excited to see this launch. I have been following for quite some time and I'm really excited Wasp progressing so well!
I know it's probably way down the priority list, but are you planning to add support for multiple backends?
I've figured I've built many small apps in backend and frontend is always super ugly because I don't bother connecting React app to the the Flask app 🙈.
Having something "works out of the box", but talks python in backend would be a great workflow.
@mario_kostelac that would be awesome indeed, and is a big part of our vision! In the short term, while rushing for 1.0, we will most likely stick to just 1 backend (NodeJS) in order to get that out and stable, but after that we will certainly start seriously looking into multiple backends.
One intermediate solution is not having a full blown support for other languages, but supporting them as "jobs" (check Job in Wasp). Then the next step is fully supporting them, which will require more effort but is doable.
I think most likely candidates are go and python. We might also look into ways to enable community to develop these backends on their own.
This is really interesting! Great job Wasp team!
I've built a lot of web apps of different shapes and sizes and I can see how Wasp could be useful in providing a standardized way to do it. Boilerplate code, as much as it is future-proof, usually slows down the initial development and makes it less challenging. Wasp comes in pretty handy to make the development faster, engining, but also future-proof. As far as I can see, Wasp DSL is well organized and gives an easy and simple to extend it with custom logic which is super important.
It might be especially useful for junior engineers to get started too. Starting with a single thing is way easier and faster than N things.
Btw what are you using for state management, how does it work in Wasp?
@lastre We are using react-query for interaction between client and server, and that actually mostly takes care of state management. Most people are quite happy with that + React Context. But, in case when that is not enough, users can go for Redux or some other solution as an additional state management solution! If we realize a lot of people are adding something custom we might also add support for it directly, but right now this seems to be ok balance.
@martin_sosic Awesome! React Query (with React Context) is more than enough. It is great that you can go with an additional state management solution because sometimes I tend to use Recoil instead of Redux because it is more fun to work with :D
@lastre Recoil does sound fun, I remember watching video about it. I got a feeling that it is made for apps that have a lot of duplicated / connected UI that needs to be kept in sync, which can become cumbersome in Redux, but I never go the situation where I needed. But am looking forward to giving it a try at some point! In the meantime yup, RQ + Context do a really nice job! And this comes from ex Redux user.
I used Wasp to win a hackathon this year - it was such a pleasure to use! I’ve done plenty of hackathons before where I’ve built small SaaS apps, and there’s just so much time wasted setting up common utilities - stuff like user management, databases, routing, etc. Wasp handled all that for me and let me build out our web app in record time.
Also, deploying the wasp app was incredibly easy - I didn’t have time to stand up full infrastructure in the 2 day hackathon and don’t have an infra/devops background, but I had something running on Netlify within an hour. Other projects at the hackathon struggled to do this, and putting access in the hands of the judges certainly helped get us 1st place.
@matijash @martin_sosic keep up the great work.
@martin_sosic @julian_laneve Thank you so much for the kind words @julianlaneve, always a pleasure to hear from you :) Really glad you find Wasp useful and we can't for you to try Beta out! :)
Way to go Wasp team! I've been following Wasp even before Alpha, when everybody still thought this was a crazy idea 🙂 Amazing to see how far you've come and the future looks bright!
So exciting to see the Beta live, packed with a ton of amazing improvements. Let's make this product of the day! :D Keep up the good work, Martin and Matija!
So much progress so far! This looks amazing 🙌 Can’t wait to build a small app with wasp 🐝
I spent the one weekend building with Wasp and it was amazing, a real pleasure. I normally develop in Vue.js, but in a weekend I had time to learn Wasp, React and finish a full-stack app (only missing styling). This would have been impossible before.
So glad to see Wasp in Beta! 🍻
@joanreyero Thanks! I remember when you pinged us with your Wasp app, it was impressive what you did with Prisma to go around some of the Wasp's rough points -> we learned a lot from that!
Super excited we got this far, I still remember when I said that if we ever get to the point where somebody makes something with Wasp, that is it, we made it - but it won't happen :D. And now we are already so far beyond that!
Long road still ahead, but so far it has been amazing, and kudos to the whole team for bringing all this together and making it happen. Full speed ahead!
For a developer like myself who is building a lot of different web applications, I know how much time I am losing just setting up the project without a single line of business logic being written. That is why I got excited about testing Wasp because all of the time I will save up and being able to present MVPs to clients faster. I noticed that Wasp reminds of Meteor.js which is great! Is there a way to share Wasp code as libraries/packages so it can be added to existing projects?
@matej_serbec1 Thank you for kind words! Meteor was certainly an inspiration in big part, they made the biggest progress in the world of full stack JS solutions, and really innovated.
Wasp let's you use JS / React / Node / ..., so you can normally use npm packages and share code that way. It would be super cool if you could share actual Wasp code, in the sense that you write a feature for Wasp app that consists of .wasp files and .js files and similar, and that share that whole thing as a package, but we are not there yet -> but it is in plans! Personally I am really looking forward to that and we have some early ideas. I am thinking it might follow somewhat what RoR is doing with Engines: https://guides.rubyonrails.org/e... .
Congrats Matija, Martin and the Wasp team. Nice accomplishment. Keep up the hard work!
LeadDelta professional relationships CRM