Dejan Mircevski
Dejan Mircevski
> Adapters are not classes, could you rewrite to be a pure function instead? Done. > Polyfilling sounds unnecessary as well, as Next.js already does this. I presume you mean...
Rebased on top of latest `main`. @balazsorban44 PTAL.
> `fetch` is globally available in Next.js, no polyfilling is necessary. OK, but how do I get `jest` to recognize that? No matter what I try in `jest.config.js`, I get...
OK, we managed to drop the polyfill (except in testing). @balazsorban44 that's all the feedback adressed. (Also, please ignore the [vercel bot](https://github.com/nextauthjs/next-auth/pull/4573#issuecomment-1165700314); that's a temporary mistake I fixed.)
> I think there was an accidentally made change here, when you probably tried fixing some merge conflicts. This PR should only have added a new adapter but made a...
It appears that the convention is to return "" for the full path (and error message for the content) when an error occurs. This should be mentioned in the blurb.
@sunfishcode: agree that some debuggers will want to provide their own UI (eg, Brackets and IntelliJ, which already do so for JS). That requires exposing the debuggerdebuggee interface as a...
Pavlo said it was implemented in the latest release.
> The type deletion problem is _perhaps_ unrelated It is definitely unrelated. > but what does the warning mean? An SQL query we generated took way too long; we should...
@mpdehaan is this a duplicate of #1180? > It makes it look like there was a slow query, which I suspect was not the case What happens when you perform...