QubitProducts/gcs-browser-upload

Issues

• It doesn't resume upload after restoring internet connection,

  #35 opened a year ago by aqib008
  0

• Context for usage example?

  #11 opened 8 years ago by danielcompton
  5

• Resumable upload will not resume properly if we try to resume multiple times with the same file.

  #29 opened 4 years ago by deepika06
  0

• Signed Url example?

  #28 opened 4 years ago by dmccarty
  1

• async/await is supported by major browsers for many years now, can we remove regenerator-runtime dependency ?

  #26 opened 5 years ago by nojvek
  0

• Missing license file

  #24 opened 5 years ago by dragly
  1

• Fix memory leak

  #4 opened 5 years ago by oliverwoodings
  0

• Idea: Support AWS S3

  #15 opened 6 years ago by svengau
  2

• Compile ES6 to standard JS

  #16 opened 6 years ago by nidhalkratos
  3

• Possible to support non-browser environment?

  #14 opened 6 years ago by f1cognite
  1

• Getting a CORS error

  #13 opened 6 years ago by hendrikswan
  5

• Remove fileId option, use upload URL instead

  #8 opened 9 years ago by oliverwoodings
  0

• Error should be thrown if resume validation fails

  #7 opened 9 years ago by oliverwoodings
  0

• Publish to NPM

  #6 opened 9 years ago by oliverwoodings
  0

• Upload in a web worker so we can truly persist across reloads

  #5 opened 9 years ago by oliverwoodings
  0

• Add restricted exponential backoff when 500 errors occur

  #3 opened 9 years ago by oliverwoodings
  0

• Use data from response range header

  #2 opened 9 years ago by oliverwoodings
  0