Thread by @aleksandrasays

🔥 Announcing @BLITZ_JS 2.0 BETA 🔥

✨ The Missing Fullstack Toolkit for Next.js ✨

✅ Blitz RPC — typesafe e2e API layer without fetch or res.send()
✅ Blitz Auth — battle-tested & more flexible than next-auth
✅ Conventions & Codegen — set up a full app in 2 mins

Previously Blitz abstracted Next.js, but Blitz 2.0 is now a modular toolkit that plugs into any new or existing Next.js app.

Blitz picks up where Next.js leaves off, providing battle-tested libraries and conventions for shipping and scaling worldwide apps 🤯

1️⃣ Typesafe API Layer

Build & iterate on features much faster than REST, GraphQL, or vanilla API routes because you don't have to mess with HTTP, fetch, res.send(), or serialization.

It feels like using plain functions instead of HTTP API. Easily inspect, customize, & test 🙌

2️⃣ Authentication & Authorization

👉 Powerful, flexible, and battle-tested authentication and authorization for Next.js

👉 You get more control with simpler APIs than next-auth or other alternatives

👉 Easily add third-party social integrations like Google, GitHub, and Auth0

3️⃣ Conventions & Codegen

Set up a new app in 2 mins instead of 2 weeks. Everything will be set up for you, including auth, user signup, forgot password, and your form library of choice.

4️⃣ Route Manifest

✨ THIS SOLVES TYPESAFE ROUTING IN NEXTJS ✨

Blitz's Route Manifest has three main benefits:

✅ Type safety
✅ Prevents broken links
✅ Allows you to move pages around without having to update hardcoded URLs

5️⃣ Production-ready

Blitz.js 2.0 Beta is ready for production testing 🔥

We're using it in prod at @Flightcontrolhq, and so are many others. The core code was migrated from legacy Blitz, so we don't expect any issues. In fact, Blitz beta should have fewer bugs than the legacy

Going forward, our mission is to be the most trusted technical resource for rapidly building and scaling full-stack TypeScript apps.

We're doing that through frontend-agnostic libraries that simplify complex app problems with minimal tradeoffs and through full-stack guides.

I know how cool this all sounds, but you’re probably freaking out about how long it will take you to migrate the legacy Blitz codebase to the new Blitz 2.0.

We got you covered! 🎉

Over the last few weeks, @dillonraphael put A LOT of effort into our upgrade codemod, ensuring it works for most codebases.

Massive shout out to Dillon and everyone who ran the codemod on their Blitz app and gave us precious feedback 🙌 🙌 🙌

The upgrade-legacy codemod automatically converts your codebase to the new Next.js + Blitz 2.0 setup.

Give it a try by running the following command inside your Blitz project:

(You can also check out our docs to learn more about the upgrade: blitzjs.com/docs/upgrading…)

There are still lots of new features coming 😎

If you have any questions, ideas, or issues, post them on Discord or GitHub.

🔗 Docs: blitzjs.com
🔗 Discord: discord.blitzjs.com
🔗 GitHub: github.com/blitz-js/blitz

We love our community and appreciate all of you deeply. We couldn't have done that without you!

Thank you all for the feedback, contributions and for being a part of the Blitz community 🙏

PS. We moved the legacy Blitz framework code to a separate repository. If you have any issues regarding the legacy framework, post them here: github.com/blitz-js/legac….