Max Greenwald

@lpinca I'm worried that the proposed client auth solution enforces `noServer: true` and adds boilerplate to the auth process. I currently use an externally defined server and want to continue...

@lpinca Thanks for the reply! I agree that the solution proposed by @zoltan-mihalyi is good and fits most use cases. If that is a "supported" solution, then `verifyClient` should not...

@lpinca Gotcha, that makes complete sense. Thanks for the clarification!

I don't think Next.js is going to / can deprecate per-page `getInitialProps`. Even if they don't include that exact method in the upcoming layouts proposal, they MUST include a way...

This may be a duplicate of #209 and #210...not sure though

Does this also solve https://github.com/vercel/next.js/issues/38273?

Seems like the Rust SQLX project encountered the same issue and was able to solve it (mostly?) using `EXPLAIN VERBOSE`: Issue: https://github.com/launchbadge/sqlx/issues/367 PR: https://github.com/launchbadge/sqlx/pull/566 +1 on what @FrigoEU said: `pgtyped`...

@ojj1123 Updated to clarify: This **also** happens when I add a `loading.tsx` file. Agreed that this likely would happen with `useQuery` and `suspense: true`, but I haven't tried that.

> For some reason, the fix is to have at least one boundary. Yea, after playing around with it a bunch I concur this can resolve the infinite loop (though...

> yes, but this re-run doesn't trigger suspense again. Once data is in the cache, we never throw any promise again. So this can't be the problem imo Ok, very...