Joseph

Looks like there a bunch of e2e tests to fix?

I reckon we should return an empty body for HEAD requests here? https://github.com/vercel/next.js/blob/f0653d4a45807a8d239eccb00e34f40c3cece71a/packages/next/src/server/image-optimizer.ts#L1092-L1095 ```ts if (req.method === 'HEAD') { res.end() } else { res.end(buffer) } ```

You'd need to defer the function call to runtime. ```tsx import { connection } from 'next/server' import { Suspense } from 'react' export default function Page() { return ( )...

Didn't mean to leave ya hanging here, I just didn't have any good option, I forwarded this issue to the team. I kept going back to: if your build pipeline...

Hi, Yes this one is a bit tricky cuz the `node:sqlite` (or other variants) module does sync operations, it blocks I/O. You can add await a connection to force it...

> I initially thought this behavior was a bug because, according to the documentation, with Cache Components all pages in the App Router are dynamic by default. Under that model,...

> I’m experiencing the same issue, and the current behavior seems inconsistent with the App Router’s “dynamic by default” documentation. Please do checkout the current version of https://nextjs.org/docs/app/getting-started/cache-components#automatically-prerendered-content: We now...

Hi, client components can't be async. What are you trying to accomplish here?

Mm yeah, I'd rephrase the title to, build step should error when async components are present in client graph, or something like that. I am no expert on the bundler...

@diogomartino do you observer the same if you downgrade to 15.2.0 or earlier?