I've been tinkering with redwood.js for the last couple of months. I quite like it and it definitely speeds things up, compared to rolling out everything yourself. But since this is alpha-grade, there have been a lot of breaking changes -- which I totally understand, but it's been PITA to work on upgrades vs my side project. To the point: how does the upgrade situation looks like with Blitz.js? What are the plans for breaking changes now that's in a beta? Also, what would be the biggest differences between redwood & blitz (besides blitz being based on next)?<p>Lastly, thank you for working on this project/problem, definitely a lot of potential here. I've also seen that you really care about the community around the project, which is awesome!
I have been a tad skeptical about how Blitz.js would accomplish "batteries-included" elegantly, but 5 min into reading the (very thorough) docs and it seems like a fantastic amount of abstraction to work with. You're a genius flybayer!<p>2 questions:<p>1. How the docs read right now, I'm cautious about the "recipes" concept. It's not clear why I'd need to use a recipe to install Tailwind instead of installing Tailwind via NPM. I'd love the docs to explain what "coupling," if any, occurs with Blitz <> a recipe's dependencies, so I can better understand what I'm opting into by choosing the framework.<p>2. Is there a roadmap for API-only implementation, like Rails? If I want to use some of my Blitz endpoints from another client is that possible?<p>Thanks!
This sounds very cool but the code sample on the front page didn't have instant appeal for me.<p>Once I Googled a little and found out what it was doing it looked awesome, but it was very noisy if you don't know the components of Blitz.<p>Compare it to this code from early in the ActiveRecord guide:<p>"class Product <<p><pre><code> ApplicationRecord
</code></pre>
end"
The one thing that was holding me back from going forward with Blitz is the rapid amount of changes, so this is very exciting. I'm using NextJS with NextAuth and Prisma right now, but I want it more integrated with more of a server aspect to host. Blitz is such a great idea.<p>Congrats on the beta!
TL;DR Give Blitz a try.<p>I've been developing my app with Blitz. It has been an extremely productive framework to work with.<p>The following are a few of the productivity boosts that I like:<p>1. It includes authentication plus there's a good library for authorization (blitz-guard) so auth is a breeze.<p>2. The generator is helpful when I started with Blitz, but use it less now.<p>3. The community is friendly and helpful. ex. Check out this post on skeleton loaders <a href="https://andreas.fyi/engineering/nextjs-auth-skeleton-loaders" rel="nofollow">https://andreas.fyi/engineering/nextjs-auth-skeleton-loaders</a><p>4. The integration with Prisma is buttery smooth. In your UI code you call a function that has the database access. Blitz converts the function calls into API calls and runs your database code on the server. When Prisma is not enough you can drop to `db.$queryRaw` to write SQL directly.<p>5. Personally, I dislike fiddling with 800 libraries to get a project up and running. Blitz includes Jest, Prettier, and everything else you need so on so that you're productive from day 1.
I've tinkered with this in side projects and it's really a joy to work with. The setup for a basic CRUD app w/ GraphQL and Auth/plugins/CSS frameworks takes ~1minute, and the generated code is pretty extensible.
Is there a possibility to scale Blitz.js based applications? It seems as if there is some stateful behaviour to achieve the deep integration of logic between back- and frontend. Would scaling be possible with sticky sessions?
Just tried it my my team, it looks promising. You can literally make the full stack app in 5 minutes using Blitz. It supports SQLite, PostgreSQL an MySQL out of the box.
This is pretty cool but the thing that all JS frameworks seems to miss out is an admin area. Why?<p>This is one of the main reasons I'll continue to pick Django as a back-end. Django + DRF does pretty much everything you would ever need from a framework with the added bonus of a fully working and customizable admin straight out the box.
Amazing!! The idea to generate an API when compiling is very good.<p>The only thing that is holding me back is that as far as I understand Prisma doesn't support cascading deletes.<p>Meaning that if I have to delete a user, then I have to manually delete all his projects, comments, posts, etc... which is not nice.
Can a backend for Cloudflare Workers become available?<p>Workers does not support Node APIs (<a href="https://developers.cloudflare.com/workers/learning/how-workers-works" rel="nofollow">https://developers.cloudflare.com/workers/learning/how-worke...</a>)<p>There is documentation of deploying a NextJS app (<a href="https://developers.cloudflare.com/pages/how-to/deploy-a-nextjs-site" rel="nofollow">https://developers.cloudflare.com/pages/how-to/deploy-a-next...</a>)
Been using in hobby projects for a bit now, absolutely fantastic framework, especially the data handling. It also gives you a few goodies by default that Next.js doesn't.
What does the `Zero-API` data layer abstraction imply? Asking because I want to understand if the frontend and backend can be deployed on different web servers.
Amazing how fast this is moving, congrats! Looking forward to seeing it being used more broadly.<p>Just saw that they have links to "Made with blitz" on their wiki in case anyone is interested:
<a href="https://github.com/blitz-js/blitz/wiki#-made-with-blitz-include-link-to-repo-if-open-source" rel="nofollow">https://github.com/blitz-js/blitz/wiki#-made-with-blitz-incl...</a>
> At build time, that function import is swapped out with an auto generated HTTP API.<p>This was surprising to me, I thought it would be focused on SSR.
This sounds very interesting to me as my team has had some real struggles figuring out how to deal with things like authentication in Next.js. In one case, we've rolled our own oauth with a completely separate express api. In another, we still haven't quite decided. I've been on the lookout for a sort of Node equivalent of Rails.
In the spirit of Rails, does Blitz include a repl analogous to irb? Something that automatically loads in your models and maybe config?<p>It’s been a while since I’ve used Rails but that interactive environment was my favorite way to get familiar with activerecord models.
This is one of the things I'm most excited about for frontend development. Glad to see it's in beta!<p>Will have to give this more use on something beyond "Hello World" soon.
Does blitz have typescript support? I’ve looked everywhere on the site and there’s no mention which is a bad sign. It’s too hard to build large apps with vanilla JavaScript