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

map-filter

v1.0.0

Published

Double loops suck.

Downloads

5

Readme

map-filter

Build Status

When you need to run map and filter together (aka elegant reduce).

Why

I've seen code that looks like:

let list = [
  {name: 'alex', age: 28},
  {name: 'frank', age: 28},
  {name: 'joe', age: 30},
  {name: 'ayham', age: 28},
  {name: 'solomon', age: 29},
]

list.filter(p => p.age < 30).map(p => {name: p.name}) // youngsters!

Whereas you can achieve much better performance with a simple reduce:

list.reduce((acc, p) => {
  if (p.age < 30) {
    acc.push({name: p.name})
  }

  return acc
}, [])

No trust? Check yourself:

~/projects/js-map-filter (master ✔) ᐅ node bench.js                                                                                                                                                                                1s
filter + map: 19.378ms
reduce: 6.254ms
map-filter module: 7.116ms

So what does this guy do?

This utility lets you do the same things you'd do with a reduce, without having to keep track of the accumulator:

const mapFilter = require('map-filter')

filterMap(list, p => {
  if (p.age < 30) {
    return {name: p.name}
  }
})

Just return undefined (aka don't return) for the values you want to exclude from the final list.

Tests

Just mocha it:

~/projects/js-map-filter (master ✘)✹✭ ᐅ mocha                                                                                                                                                                                      1s


  mapFilter
    ✓ should be able to return all original values if no fn is specified
    ✓ should be able to exclude values
    ✓ should be able to map values
    ✓ should be able to handle falsey values


  4 passing (9ms)