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
After finishing #25, I decided this package doesn't make sense anymore because of a new API: image.decode()
// preload image
- loadImage(url)+ img = new Image()+ img.src = src
// load and await image
- await loadImage(url)+ img = new Image()+ img.src = src+ await img.decode()
Any reason for this module to continue existing? Its utility is mainly around the ability to create images from strings and await them:
awaitloadImages([a,b,c])
But that's not a great API if one of the loading fails, you might want to implement your own retry mechanism or just ignore them. Instead the whole promise fails.
So should it just return an array and have you deal with them via Promise.allSettled()? At that point the advantage is minimal, and not really matching the package name.
After finishing #25, I decided this package doesn't make sense anymore because of a new API: image.decode()
Any reason for this module to continue existing? Its utility is mainly around the ability to create images from strings and await them:
But that's not a great API if one of the loading fails, you might want to implement your own retry mechanism or just ignore them. Instead the whole promise fails.
So should it just return an array and have you deal with them via
Promise.allSettled()
? At that point the advantage is minimal, and not really matching the package name.The text was updated successfully, but these errors were encountered: