Joseph
Joseph
Hi, are you using a Dockerfile to build/develop? Make sure you are not copying to the root of the image file system.
Not sure about that, I have made a PR to try and fix the issue I found in another report, if that gets merged, we can try it out against...
The PR got merged, you should be able to try with latest canary to see if it helps :)
It'd be interesting to narrow down - Perhaps unrelated to this case, but someone also identified a memory leak with fetch - https://github.com/vercel/next.js/pull/82678 Unlikely related as you can't even start...
I mean, we are here now - might as well try to binary search the canary that did it - there's 130 canaries, we can resolve this in about 7-8...
HI, so - let's try this one trick, replace the `next` version in `package.json` with `https://vercel-packages.vercel.app/next/commits//next` I'd say, first verify that the first commit hash - which happens directly after...
Aha, but ok that was just guessing on my side - so you can binary search from 1429d72 onwards - we are closing on the commit that introduced the issue....
@NeoSahadeo nice! would be nice to know what happened though - I guess 15.5.0 did the trick, the other two have not had any changes that would be related to...
> Hello @icyJoseph , could you please take a look at my PR for this issue: #84017 ? Thanks! Hi, no need to tag me again. I've been tagged in...
I am already seeing some things to comment. We should take this opportunity to start referring to the `next.config.js` file, as `Next.js config file` - since today it can be...