Joseph

https://github.com/vercel/next.js/issues/41988 I see now.... the payload on this one is about 300kb

When deploying to Vercel, on [email protected], I still see this problem. - The enableUndici flag is still needed, even locally though - In Vercel, when the flag is active and...

I have a page which shows data from a cookie, but the data is only fresh upon hard loading of the page. SPA transitions into it do not trigger a...

I actually observe no issues now with `13.0.1`. I am not really sure how it got fixed though. I don't even need to `force-dynamic` which is lovely.

You kinda need to get a hold of where these are used and sprinkle `use client` directives.

I think a fix is upcoming, but pretty much the issue is that TypeScript doesn't understand async components... It always expects JSX as child, not `Promise`. Many are type casting...

I do believe `error.tsx` must be client components... According to docs: https://beta.nextjs.org/docs/routing/error-handling#error-boundaries  So while this is working as expected, perhaps a better error message...

> What would be workaround in case I want to catch errors inside [id] page? Mmm perhaps a proper client component to handle the error. As shown in the docs,...

> The above workaround breaks when using `experiments.layers = true` because even though the module ID is named, a chunk hash is still appended to the output assets. The only...

> @icyJoseph is it breaking when you try and deploy it on Vercel? The snippet is working for me in Next 12 for both dev and prod build _locally_. However...