File Upload regression with @urql/exchange-graphcache 2.2.6

[BjoernRave]

When installing the latest version of @urql/exchange-graphcache my file uploads to the apollo-server changed from looking like:

interface File {
  filename: string
  mimetype: string
  encoding: string
  createReadStream: () => any
}

file: Promise<File>

to:

interface File {
path: string
}

file: File

Now I cannot access createReadStream anymore and thus not pass the file to s3 to upload

[kitten]

Hiya👋

Do you have a CodeSandbox (without any API / server will do)
Also are you using @urql/exchange-multipart-fetch or something else for uploads?

[BjoernRave]

@kitten I am using @urql/exchange-multipart-fetch. Will work on a codesandbox now.

Codesandbox: https://codesandbox.io/s/urqlexample-ssr-with-nextjs-eg660

[JoviDeCroock]

That codesandbox doesn't seem to show any issues in terms of what's being sent.

Is there something I'm missing @BjoernRave

[BjoernRave]

@JoviDeCroock the problem is what I receive on my server, not what get's send.
It works fine with @urql/[email protected], but not with @urql/[email protected].

[email protected] and @urql/[email protected] work fine

[JoviDeCroock]

So are you saying that if you leave graphcache out with the latest urql it works or is it specific to graphcache? It's very hard for us to analyze what goes wrong since we can only see that it sends a binary in the sandbox.

When you would add graphcache 2.2.5, it works as well?

[BjoernRave]

@JoviDeCroock ah, seems like you found the problem.

Thanks alot for that :)

And yes it works fine with @urql/[email protected]