res.body.getReader is not a function on vercel about chatgpt-api HOT 7 CLOSED

@leecobaby can you verify the version of chatgpt package you're using?

Hello, I was submitting an issue with v2.0.1, but now my project is working after upgrading to v2.0.4.
Thank you so much for the fix. 🎉

from chatgpt-api.

Thanks for the report, Leeco.

I'm guessing this has something to do with either Vercel's eager lambda bundling leaving out undici, which we import asynchronously — or undici itself within this environment.

Needs investigation.

from chatgpt-api.

Related:

• vercel/next.js#32357
• https://stackoverflow.com/questions/57664058/response-body-getreader-is-not-a-function

It's possible that the Vercel environment is polyfilling fetch with node-fetch, which would cause this error.

from chatgpt-api.

@leecobaby can you verify the version of chatgpt package you're using?

from chatgpt-api.

I have a tentative fix released in https://github.com/transitive-bullshit/chatgpt-api/releases/tag/v2.0.3

I think the issue is that Vercel's Next.js Node.js environment polyfills fetch with the non-standard node-fetch, which was breaking support for the streaming response support. I've aded a special case to test for this and handle it gracefully.

Please let me know if you're still experiencing issues after upgrading to latest.

from chatgpt-api.

Update: I meant v2.0.3. There was a problem with v2.0.2.

from chatgpt-api.

That's great to hear 💪

I've also verified that the package works as expected using both next dev locally as well as when deployed to Vercel as a serverless function. I haven't tried it out on edge functions yet.

from chatgpt-api.