Samuel Batista

We should be careful to only use functionality that is compatible with `next export`: https://nextjs.org/docs/app/building-your-application/deploying/static-exports AppRouter is fine, but I recommend not tying this project to any backend functionality from...

> @gamedevsam `next export` afaik is to make a static export of you app. If we just wanna self host somewhere, that doesn't need to be static. There are plenty...

> Next's canary versions are usually pretty stable but sure we can go with stable for now, not considerably different. I don't agree with this perspective. We want to ensure...

> > We should be careful to only use functionality that is compatible with `next export`: https://nextjs.org/docs/app/building-your-application/deploying/static-exports > > AppRouter is fine, but I recommend not tying this project to...

> > I don't think this is a use-case we should be facilitating for. You can't just deploy on Vercel with no configs since you need a at least a...

Now this change I support. I

@ExplorerAadi are you sure this is a good idea and aligned with the long term interests of the project? What value do we get from introducing app router and leaning...

@ExplorerAadi don't mistake my enthusiasm for Maybe with decision making power, or authority of any sort. As far as I know @Shpigford is the sole decision maker (he has merge...

Any reason why this shouldn't get merged? Seems like a useful fix.

Looks like this repo maybe stale, it's worth trying to make a fork the canonical / active version of the package. We might be able to reach out to NPM...