Blitz will be pivoting to a framework agnostic toolkit that preserves the world-class DX and features we adore but brings it to all Next.js users and optionally Remix, SvelteKit, Nuxt, etc.
Your existing Blitz apps will continue to run, and we will fix any critical bugs that come up. The current Blitz codebase will remain. It may move to a different repo, but it will be preserved and we can continue to make releases as needed. We'll strive to make the migration to the Blitz toolkit as seamless as possible.
Nope - we are working to make the new setup as close as possible to the current setup. For any changes required, we will have a codemod that will automate all, or almost all, of any changes required. The effort on your part should be minimal.
Yes, for sure you can start new Blitz apps. Nothing has changed with the current framework, and the future migration will be seamless. The productivity boost from Blitz will put you way ahead of manually sourcing your own Next.js stack from scratch, even with the coming migration.
No! Go ahead and ship your Blitz app to production with confidence. We'll continue to fix any significant bugs.
Blitz toolkit will be meant for building anything with a database, from side projects to massive enterprise apps. It will both enhance fullstack DX and provide the missing backend components for JS that Rails and Laravel enjoy.
We believe the core value that Blitz currently provides is:
A new toolkit would start with these as the foundation. We think almost everything Blitz currently adds would be migrated to the toolkit including recipes, typesafe Routes manifest, etc. Then we’d start shipping a ton more awesome things.
For more details check out the Blitz Pivot RFC. It goes into detail on why this is happening. It includes an outline of the toolkit, and a list of the features we’d like to add.