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

image-juggler

v1.0.0

Published

Juggle pixel data between different web containers, like <img>, <canvas>, ImageData, File, ArrayBuffer, Blob, Array, etc.

Downloads

3

Readme

image-juggler

The web has some nice image-processing capabilities, but the APIs are wildly inconsistent. Plus, some third party libraries want a canvas, others want an image. And if you need to read an image in, you need to know the intimacies of the File and Blob APIs.

Usage

Accept an image File via an <input> tag, and append it to the document as an Image.

var jug = require('image-juggler');

var img = document.createElement('img');

var input = document.querySelector('input[type="file"]');
input.addEventListener('change', function(e) {
  e.stopPropagation();
  var file = e.target.files[0];

  if (!file) {
    throw new Error('No file or invalid file was selected');
  }

  jug.fileToImage(file, img, function(err, img) {
    document.body.appendChild(img);
  })
}, false)

API

Each of the functions follow the format of function(input, opt_output, callback), where:

  • input: the thing coming in...
  • opt_output: if part of the signature, this element is used as the target container of the transform operation. For example, imageToCanvas(image, opt_canvas, cb) will use opt_canvas, but if none is passed in it will create a new <canvas> and supply it to the callback. Supplying an existing element can help to avoid GC. Some operations, due to the underlying implementation, require a new object to be created regardless (such as ArrayBuffers).
  • callback: Always of the signature: function(error, result), even if the underlying operation is not asynchronous. NOTE: There is no guarantee that callback will be called asynchronously. Yes. This releases Zalgo.

imageToCanvas(image, opt_canvas, cb)

imageToArrayBuffer(image, cb)

imageDataToImage(imageData, opt_image, cb)

fileToArrayBuffer(file, cb)

fileToImage(file, opt_image, cb)

canvasToImage(canvas, opt_image, cb)

blobToImage(blob, opt_image, cb)