[RFC] Time to maintain a fork of Next.js? · blitz-js/blitz · Discussion #1990Problem Our custom compiler approach has done fairly well thus far, but we are reaching its limits. Currently we compile a blitz codebase into a next.js code base (inside .blitz/build) and then run next from .blitz/build. This allows us to override and customize most things about next.js. But honestly this is a bit hacky and introduces a whole slew of problems that we have to try and work around.
![[RFC] Time to maintain a fork of Next.js? · blitz-js/blitz · Discussion #1990](https://cdn-ak-scissors.b.st-hatena.com/image/square/69226936d860cb586c6a8145ed46a94f16e5537b/height=288;version=1;width=512/https%3A%2F%2Fopengraph.githubassets.com%2Fa64d16c0f42dc4e43f4976f50e336ef580aff2b8621c02765437270097cc0e19%2Fblitz-js%2Fblitz%2Fdiscussions%2F1990)
GitHub - blitz-js/blitz: ⚡️ The Missing Fullstack Toolkit for Next.js
