npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

async-image-loader

v2.0.3

Published

a small utility to load image tiles in parallel

Downloads

110

Readme

async-image-loader

unstable

A small utility to load images asynchronously, with progress events and simple error handling.

Examples

At its basic form, it can be used to load image URLs.

var load = require('async-image-loader')

var images = [ 'foo.png', 'blah.png' ]
load(images, function (images) {
  // by default, "not found" images will be null
  images
    .filter(Boolean)
    .forEach(function (img) {
      document.body.appendChild(img)
    })
})

Here is a more complex example, where each "tile" holds some data in an object. The same object will be passed to "progress" events as ev.data.

var loadTiles = require('async-image-loader')
var canvas = document.createElement('canvas')
var context = canvas.getContext('2d')

var tiles = [
  { url: 'foobar.png', x: 0, y: 0 }
  { url: 'some-tile.png', x: 50, y: 50 }
]

loadTiles(tiles, {
  crossOrigin: 'Anonymous',
  defaultImage: defaultImage
}).on('progress', function (ev) {
  console.log("Progress: ", ev.count / ev.total)
  
  // stitch the image onto canvas
  context.drawImage(ev.image, ev.data.x, ev.data.y)
})

Install

npm install async-image-loader --save

Usage

NPM

emitter = loader(urls, [opt], [cb])

Starts loading the specified urls. Elements in the urls array can either be strings, or objects containing { url }.

The opt settings can be:

  • crossOrigin the CORS setting for image loading (default undefined)
  • defaultImage the fallback Image to use when a load 404s (default null)

On complete, cb is called with an array of HTMLImageObjects as the first paramter (same order as input). Any images not found will be replaced with defaultImage, or null.

emitter.on('progress', fn)

Each resource will trigger a progress event when it completes loading, or when it fails. The function is passed an event parameter:

{
  total: Number        // total # of images,  N
  count: Number        // # of loaded images, [ 1 .. N ]
  image: Image         // loaded image element, or defaultImage
  data:  String|Object // the value provided in the input array
}

Since the loading is done in parallel, the order is not the same as the input. This event will be triggered regardless of whether the image resource loaded successfully, so image may be null.

Here, ev.data is the same element that was given in the input array, either a string URL or the object containing { url }.

emitter.on('not-found', fn)

Emitted for each resource that cannot be loaded (i.e. 404). The passed value is the data that was unable to load; either a String or { url } object depending on what was passed to input.

This is emitted before the progress event.

License

MIT, see LICENSE.md for details.