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

@team-griffin/capra

v2.0.0

Published

Common utilities

Downloads

8

Readme

@team-griffin/capra

We can do a lot of cool stuff with the latest ES spec. Rest/spread, Object.entries, etc. For 90% of what lodash/underscore/ramda provides you can easily accomplish with native javascript now. Capra's aim is just to cover some of the more awkward computations that aren't out-of-the-box yet.

These methods are written for post-IE browsers so they're very small and very performant.

map-obj

(obj: object, fn: (key: strng, value: any) => [ string, any ]): object

Calls fn with each key/value of obj. Expects a tuple of newKey/newValue in order to construct the return object.

before

Object
  .entries(obj)
  .reduce((acc, [ key, value ]) => {
    const [ newKey, newValue ] = fn(key, value);
    return {
      ...acc,
      [newKey]: newValue,
    };
  }, {});

after

mapObj(obj, fn);

filter-obj

(obj: object, fn: (key: string, value: any) => boolean): object

Filters out object properties based on the predecate function.

before

Object
  .entries(obj)
  .reduce((acc, [ key, value ]) => {
    if (fn(key, value)) {
      return {
        ...acc,
        [key]: value,
      };
    } else {
      return acc;
    }
  })

after

filterObj(obj, fn);

invert-obj

(obj: object): object

Inverts the key/value pairs of an object.

before

Object
  .entries(obj)
  .reduce((acc, [ key, value ]) => {
    return {
      ...acc,
      [value]: key,
    };
  }, {});

after

invertObj(obj);

omit

(obj: object, keys: string[]): object

Omits the given keys from an object.

before

const {
  foo,
  bah,
  ...withoutFooBah,
} = obj;

after

const withoutFooBah = omit(obj, [ 'foo', 'bah' ]);

assoc-path

(obj: object, path: string[], value: any): object

Adds a property at a deeply-nested level. This was an ugly mess of spread properties and was hard to do dynamically...

before

{
  ...obj,
  foo: {
    ...obj?.foo,
    bah: {
      ...obj?.foo?.bah,
      baz: 'baz',
    },
  },
}

after

assocPath(obj, [ 'foo', 'bah', 'baz' ], 'baz');

group-by

(arr: any[], fn: (v: any) => string): object

Groups an array based on the given predecate

before

not really possible with native methods

after

groupBy(arr, (x) => x.category);

is-empty

(a: any): boolean

is-nil-or-empty

(a: any): boolean