-
Notifications
You must be signed in to change notification settings - Fork 30k
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
options for FileHandle.readableWebStream()
#40606
Comments
+1 to this. It would be a good addition. |
The whatwg spec gives an example implementation. (Below snippet incorporates some fixes I proposed to the spec, and adds in start/stop options.)
|
There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment. For more information on how the project manages feature requests, please consult the feature request management document. |
There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment. For more information on how the project manages feature requests, please consult the feature request management document. |
Is your feature request related to a problem? Please describe.
I have just found out that a FileHandle got a
readableWebStream
function. I wish to use it onfetch-blob
but i can't. I need to be able to slice a file and read from a different start/end position, much likeDescribe the solution you'd like
Similar to
fs.createReadableStream(fd, options)
you also have options to start and stop. this is what i'm currently using. It would be useful ifreadableWebStream
got them as well. for now i will have to resort to usingstream.Readable.toWeb(streamReadable)
instead...Describe alternatives you've considered
I wish we got a #39015 and #37340 implemented into core natively. This is the only two blocker we have from ditching
fetch-blob
. only usingBuffer.Blob
dose not work for us since we need to handle large files and big FormData payloads that dose not live in memoryThe text was updated successfully, but these errors were encountered: