Joseph comments

Results 197 comments of


                                            Joseph

Docs: deprecated `url.parse()` call used in custom server example

So like tracing what happens with `getRequestHandler` and the `handle` it return, we see that, the parsedUrl param is optional - https://github.com/vercel/next.js/blob/42690262d69988cd95e8317a725095f8f75f85cd/packages/next/src/server/base-server.ts#L1625-L1630 - https://github.com/vercel/next.js/blob/42690262d69988cd95e8317a725095f8f75f85cd/packages/next/src/server/base-server.ts#L845-L849 And that later in the handler...

HTTP 500 on mailformed request body for server action (JSON parse SyntaxError)

Can you post more of the error stack you got? If possible of course. Thanks in advance.

HTTP 500 on mailformed request body for server action (JSON parse SyntaxError)

Thanks. Yes this is likely someone trying to exploit that CVE. And https://github.com/vercel/next.js/issues/73220#issuecomment-3614485330 is likely the same issue, but in your case, you've tested it with the `text/x-component`, rather than...

Setting cacheComponents=true breaks Clerk sign-in route with “Uncached data outside <Suspense>” during build

I don't remember exactly why but you might need to refactor the root layout a bit: ```tsx {children} ``` Something like that - should be fine right?

Setting cacheComponents=true breaks Clerk sign-in route with “Uncached data outside <Suspense>” during build

The thing is now that the shell for your pages is just empty 🤔

HEAD requests for Next.js image return 400 Bad Request when image is not yet cached

Alright, I think I've got it, started a draft, I'll try to work on it later today. It looks like for external resources, we already use GET, but for internal...

HEAD requests for Next.js image return 400 Bad Request when image is not yet cached

Oh wow, I had totally forgot about this - we need to revive the PR I had started. I'll try to pick it up this weekend, but I think it...

HEAD requests for Next.js image return 400 Bad Request when image is not yet cached

https://github.com/vercel/next.js/pull/84180 I updated the PR, I still think there's one more item to consider (returning empty body, when the incoming request is HEAD) - might be a breaking change though...

Reached heap limit Allocation failed - JavaScript heap out of memory

hi, have you tried with another package manager, or different version of pnpm? just in case? It runs without problem here, https://stackblitz.com/github/NeoSahadeo/Avg-NextJS-experience - 🤔

Reached heap limit Allocation failed - JavaScript heap out of memory

Really strange, a project that small should just run, as the stackblitz shows - Maybe give `pnpm next dev --turbo` a go too - Got more info you could share...