Phil Pluckthun

Just to clarify before looking into this because that's an important distinction: Does it never come down and stay stuck at 800MB (I assume MB not Mb?) or does it...

Hm, ok gotcha 👍 That doesn't necessarily sound like a memory leak, but a Chrome debugger memory snapshot could show you what's being retained and what's using that memory. Generally,...

Gotcha! That's awesome. I'll have a look at the memory debugger myself this evening. Typically, I'd assume we've created some kind of promise chain or cycle here 🤔

This sounds like a duplicate of #3462. So, I'm not convinced your core version is accurate here in your report. Does that sound about right? https://github.com/urql-graphql/urql/pull/3464

This is only a preliminary review, but I'll get back to the details once we get closer to having a final implementation. I'm fine with fixing up the Vitest and...

@Nvos: Hiya 👋 Sorry for the delay. Mainly, what I got stuck on here is the setup. While I haven't normalised, rebased and checked everything for discrepancies yet, I started...

I'm not sure this is something that belongs in `@urql/core`. To be very honest, I think making several assumptions what a GraphQL document normalizes to is in a way important....

Marking this as `documentation`, since we'll simply have to document `@urql/core/internal` and its fetch source utilities.

@negezor: I just checked this against our [example](https://github.com/urql-graphql/urql/tree/main/examples/with-multipart) for file uploads and it works just fine 😅 (although noting that the example API currently is down for uploads). You can...

Again, please do stick to issues please for bug reports 😅 That said, while I didn't bother creating an issue for bug tracking for this, `@urql/[email protected]` does fix this. This...