-
Notifications
You must be signed in to change notification settings - Fork 352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
res.buffer is not a function in bun #1135
Labels
Comments
I think I've figured it out. It seems that Bun's fetch has a different API than node-fetch; However, it still seems to make sense to fix this problem, so I hope it'll remain open. To locally fix it (for me it worked at least) :
|
Thanks for the detailed report! I'll ask the team to look into addressing this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I am migrating my web app to bun, and it seems the dropbox SDK usage fails to download files.
To Reproduce
bun install --save-dev dropbox
bun dropbox.ts
Expected Behavior
I expect it to run, and print the name of my file. The file exists in the path, and is accessible to the app (the node JS app finds it and has access to it; moreover, if I use a non-existent file, I get a 409 error, and I don't in this case).
Actual Behavior
I get an error, like this:
Screenshots
N/A
Versions
Additional context
None.
The text was updated successfully, but these errors were encountered: