You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given that it's only needed for Deno & Node (and node should have a native solution soon), it should be an internal helper. We want to be able to remove it at some point.
The text was updated successfully, but these errors were encountered:
I started to look into this and if I understood well the problem, I'm thinking about a solution using Filehandle.read but it will need some change in the code because then slice method need to be async in order to read the desired slice from the file and returning it in a Blob instance.
I started to look into this and if I understood well the problem, I'm thinking about a solution using Filehandle.read but it will need some change in the code because then slice method need to be async in order to read the desired slice from the file and returning it in a Blob instance.
It should be fine to only do the Filehandle calls when .arrayBuffer() / .text() / .stream() is called. As for .size, if we pass the info to the new blob when creating it, it should be fine as well.
Or wait on nodejs/node#45188
This would help for the
commit
calls, when uploading very large files, to avoid loading the whole file in memory.Would help with #62
Technical PR.
Given that it's only needed for Deno & Node (and node should have a native solution soon), it should be an internal helper. We want to be able to remove it at some point.
The text was updated successfully, but these errors were encountered: