-
Notifications
You must be signed in to change notification settings - Fork 285
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
Release 3.2.3 doesn't work in the browser #654
Comments
Thanks for letting us know @gusajz we will check what the best way is to fix this. |
krishnasrinivas
added a commit
to krishnasrinivas/minio-js
that referenced
this issue
Dec 13, 2017
krishnasrinivas
added a commit
to krishnasrinivas/minio-js
that referenced
this issue
Dec 13, 2017
krishnasrinivas
added a commit
to krishnasrinivas/minio-js
that referenced
this issue
Dec 15, 2017
krishnasrinivas
added a commit
to krishnasrinivas/minio-js
that referenced
this issue
Dec 18, 2017
krishnasrinivas
added a commit
to krishnasrinivas/minio-js
that referenced
this issue
Dec 18, 2017
krishnasrinivas
added a commit
to krishnasrinivas/minio-js
that referenced
this issue
Dec 20, 2017
krishnasrinivas
pushed a commit
that referenced
this issue
Jan 4, 2018
dingjs
pushed a commit
to dingjs/minio-js
that referenced
this issue
Jan 7, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
Release 3.2.3 merged #646 which includes this code:
response.socket.end()
The issue is that
socket
property is available in node but not in the browser (see https://github.com/substack/http-browserify)This results in
Uncaught TypeError: Cannot read property 'end' of undefined
after each call ofputObject
andgetObject
.Thanks!
The text was updated successfully, but these errors were encountered: