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 🙏

© 2026 – Pkg Stats / Ryan Hefner

to-key

v1.0.0

Published

Stringify any value to be used as the key of an object.

Downloads

15,261

Readme

to-key NPM version

Convert any value to a string that can be used as the key of an object.

Install with npm

npm i to-key --save

Usage

var toKey = require('to-key');

toKey({foo: ['bar', {baz: {fex: 'fex'}}], one: 'two'});
//=> 'foobarbazfexfexonetwo'

This can be used for caching results when the results are predictable based on user input or other settings.

Example

We'll assume that someFn in the example does some heavy processing on whatever arguments are passed that can be avoided if we can instead return the cached value of a previous call.

var cache = {};
function myApp(one, two, three) {
  var key = toKey([].slice.call(arguments));
  if (cache.hasOwnProperty(key)) {
    return cache[key];
  }

  var result = someFn(one, two, three);
  cache[key] = result;
  return result;
}

Why do this?

Given the following:

  • A is time it takes (to-key or whatever you use) to stringify any arguments are passed
  • B is the amount of time it takes to retrieve a stored value from the cache
  • C is the time it takes your application to process arguments and store a new value on the cache

It's a good approach when (A + B) < C. In my applications. You can also use logic that conditionally uses cached results based on the complexity of the arguments passed.

Run tests

Install dev dependencies:

npm i -d && npm test

Contributing

Pull requests and stars are always welcome. For bugs and feature requests, please create an issue

Author

Jon Schlinkert

License

Copyright (c) 2015 Jon Schlinkert
Released under the MIT license


This file was generated by verb on February 16, 2015.