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

bistro

v0.1.0

Published

Lightning-fast replacement for lodash.get

Downloads

3

Readme

bistro — lightning-fast _.get alternative

Bistro safely extracts deeply nested object properties. Works 7 times as fast as Lodash get, dwarfs fast-get and object-path.

Under the hood, bistro compiles array paths into good old object && object.prop && object.prop.prop2... checks, making your code both concise and efficient. Lodash.get is fast enough, but why waste CPU cycles on property access? bistro is safe to use in performance-critical applications, like data analysis and visualization.

Usage

// Load the full module
const bistro = require('bistro');
// Or use component-based imports
const bistroGet = require('bistro/lib/get');
// Or use the ES6 syntax
import bistro from bistro;

// Compile the getter - do it once, or the magic is gone!
const getUsername = bistro.get(['user', 'name']);

// securely access
getUsername(undefined) // => undefined
getUsername({}) // => undefined
getUsername({ user: 'Ivan' }) // => undefined
getUsername({ user: { name: 'Ivan' } }) // => "Ivan"

// Or provide a default value
getUsername({}, 'anonymous') // => "anonymous"

Install using npm

$ npm i --save bistro

Benchmarks

The chart summarizes the performance of successful property access by array path at various depths. In all implementations misses are slightly slower. String paths (user.name) require parsing and memory allocation, with disastrous performance effect.

  • Default bistro.get implementation is the fat orange line.
  • lodash.get is red.
  • The other bistro-* lines are alternative implementations not included in the bundle, for me to watch out for changes.
  • fast-get and object-path are there in the bottom.

Made by Vladimir Klepov.