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

palimpsest

v3.0.0

Published

The goal of this project is to make it very easy to merge a set of pictures that are all the same size.

Downloads

32

Readme

Palimpsest

The goal of this project is to provide a framework for merging photos.

Hooks

palimpsest allows one to merge photos by write a pixel by pixel indexer. The indexer must provide these functions properties on a indexer object like {declare, allocate, assign}. These function all take the below explained input object and must return the value their explanations below indicate.

Input Object

The input object is comprised of the following attributes and represents a single pixel. It is sent to all modes as opts.

  • color: an object with {r, g, b} where each color channel is a number between 0 and 255.
  • loc: an object with {x, y, s} where x is the x coordinate of the pixel, y is the y coordinate and s indicates which image the pixel is from in the series.
  • progress: an object with {x, y, s} where each attribute is the percent version the loc eqivilant.
  • about: an object with {numSeries, width, height} where each is a number.

declare (input) -> String

Define the index key of the provided pixel. This function will be called a lot of times through out the process. Ideally it is stateless and will always return the same result. That said, if it doesn't no one will know.

allocate (key, input) -> Number

Provide the weight the pixel adds its key.

assign (key, pixelWeight, keyWeight, input) -> {r:Number, g:Number, b:Number}

provide the color the pixels adds to its key

transform (input) -> {}

This hook is optional. It is run before any other hook and is used to transform the input into a different shape. This way a preprocessing step can be done that you know will be seen by all other hooks.