.json() maximum size/length? about ky-universal HOT 6 CLOSED

That sounds awfully low. I'm pretty sure I am receiving larger JSON responses without issue.

Could you make a reproducible example?

from ky-universal.

@sholladay Indeed, and I don't know how to debug further.

See https://gist.github.com/xmflsct/0b830907422cf307c62d838bacab1f1b

I create this to run locally. When I run it, I see no console output, though the program exists. But if I remove some values from the sys.id[in], I can see console output without a problem.

For my case, I run ky on a serverless function, and there it hangs without properly exists.

from ky-universal.

I tried your gist, but used ky instead of ky-universal (easier to load from unpkg.com in the browser) and I got a successful console log. If it's not working for you, my guess is it's due some problem within ky-universal and one of its dependencies, as opposed to ky itself. Maybe node-fetch?

Could you provide more details about your environment (serverless platform and runtime version, etc.) and also try it with just ky?

from ky-universal.

Hmm, interesting.

I am building a Gatsby site hosted on Zeit Now and their serverless function. I do use only ky for my client side call to server side API hosted on Zeit Now which then I use ky-universal as I assume the different use case between them. Am I correct? Or I should use got instead?

My client side ky is pretty simple, a call to the API and get a very simple JSON response. On server side, ky-universal calls to in my case Contentful, which in above gist shows that sometime the response can be "long".

from ky-universal.

Duplicate of #8

from ky-universal.

Pretty sure this is a node-fetch bug related to how it uses streams. See discussion and linked issues in #8 for details.

I provided a workaround in #8 (comment) that you may want to look at. If you use it, please let me know if it solves the problem for you.

from ky-universal.