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

mapover

v1.0.0

Published

functionally maps over multiple arrays at the same time

Downloads

7

Readme

mapover-js

This is a quick and simple little utility that allows you to map over more than one array at a time. I'm sure we've all had times where we're getting data from two different source and the indexes match up but we can't just use .map() on one and use the index of that to use on the other one. (Okay, just kidding. You can do exactly that.) But this is just one function that does it for you.

Examples

Codepen here

Usage

yarn add mapover
npm install mapover
const mapover = require('mapover').mapover;
import { mapover } from 'mapover';

var newArray = mapover(array1, array2[, array3...], function callback(arg1, arg2[, arg3...]) {
  // return element for newArray
});

Todo

  • Make better, more robust -- this is kind of vague... (maybe work with any iterable)
  • Implement reduce & filter
  • Options (or function) to feed it to know how to handle when the arrays are different lengths. Right now it just goes until the first array fed runs out.