Neo Sahadeo
Neo Sahadeo
Are you on a Linux system? If so which kernel are you using? Got a friend running Win11 on the same project and it works fine for him. The only...
The issue is relate to something that changed from v15.4.1 and later.
Started my search now, I'll let you know how it goes
Ok, here's what I have so far. works: 15.4.0-canary.60 --yes 15.4.0-canary.95 --no 15.4.0-canary.77 --no 15.4.0-canary.68 --no 15.4.0-canary.64 --yes 15.4.0-canary.66 --yes 15.4.0-canary.67 --yes 15.4.0-canary.68 --no Looks like something in canary 68...
I started looking through the diffs. There's quite a few to go through and I don't have much experience with rust so feel free to jump in. Commit: - 67...
# Monkey Patch Well, I fixed the crashing issue by patching a few types. It seems to be causes by some sort of error because of new React. # Steps...
> 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...
Started testing canary 67..68. A super weird note, updated to [email protected] and it works perfectly. Then downgraded back to [email protected] and the problem appeared again. I'll finish up testing the...
Got the commit where the crash is introduced; [ef888e8](https://github.com/vercel/next.js/commit/ef888e8eae7246acee72ee1601dc0dfd41e88d1e) What is tested: a094280 -- ok dd958a1 -- ok 2bb8978 -- ok ef888e8 -- no 56c3dce -- ok 7a66008 -- ok