search

jimmywarting / StreamSaver.js

StreamSaver writes stream to the filesystem directly asynchronous
https://jimmywarting.github.io/StreamSaver.js/example.html
MIT License
4.04k stars 418 forks source link

Console log sw.js:54 #78

Closed msmicker closed 5 years ago

msmicker commented 5 years ago

I have streamsaver incorporated into my project and it is working; however, I get all of these console.log messages. Any ideas what these are from? Thanks in advance.

It is a react project from create react app. I tried two methods to use. Installing by npm and importing in my project. And using a script tag to a cdn hosting of streamsaver. Both result in the same messages.

jimmywarting commented 5 years ago

Should disappear now.

msmicker commented 5 years ago

Thanks, the logging is removed, but now I am getting a strange issues where txt files downloaded are truncated to different levels (repeat downloading for testing). I have a variety of files from small to large (GB). My Test file is ~170KB and shows 152KB, 156KB, etc

The issue may have been there before.

jimmywarting commented 5 years ago

Dosen't sound like a StreamSaver issue to me. If you show some code i might be able to help

msmicker commented 5 years ago

Thanks. It’s almost a straight cut/paste from the Ajax example. I thought it might be my API and wrote some scripts to stress test via curl- not to say it eliminates the possibility.

On Mon, Jan 21, 2019 at 10:55 AM Jimmy Wärting notifications@github.com wrote:

Dosen't sound like a StreamSaver issue to me. If you show some code i might be able to help

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jimmywarting/StreamSaver.js/issues/78#issuecomment-456120364, or mute the thread https://github.com/notifications/unsubscribe-auth/AO2vGUB4MWF_vJYBvWz_DjzsJ4jGqdmPks5vFeL4gaJpZM4aJ7L3 .