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

humane_list

v1.0.3

Published

A combination of array and kv structure.

Downloads

7

Readme

humane_list

Combining arrays with kv structures. It is meant to act the way non-programmers (ie humans) expect lists to act (ie usability).

  • Default index is 1, not 0.
  • This is no shift or unshift.
  • .pop( 'front' ) and .push('front', vals) to attach before first element.
  • .pop( 'end' ) and .push('end', vals) to pop/insert after last element.
  • .front() and .end() instead of .first() and .last()
    • Why design it this way? Because index positions can be -1, -2.1, etc. Non-programmers would assume .first() returned value at index 1, instead of -1.
  • Instead of index, you have positions.
    • Why?! Because non-programmers might confuse keys with indexes. Think of a book with an index.

Usage: Inserting

var ha = require('humane_list');
var stuff = new ha.Humane_List();
stuff.push( "end", "red" );
stuff.push( "end", "blue" );
stuff.end(); 
// => "blue"

Remember, index starts with 1, not 0.

stuff.alias( 1, "favorite" );
stuff.alias( "favorite", "fire_color" );
stuff.at_key( "favorite" );
// => "red"

stuff.at_key( "fire_color" );
// => "red"

Usage: Inspect

stuff.has_key( "favorite" );
// => true

stuff.positions();
// => [ 1, 2 ]

stuff.keys();
// => [ ['favorite', 'fire_color'], [] ]

stuff.values();
// => [ 'red', 'blue' ]

Usage: Deleting

stuff.delete_at( "fire_color");
stuff.delete_at( 2 ); 
// This deletes value at index 2.

No shift or unshift.

stuff.pop('front');
// => "red"

stuff.push( 'front', "red" );
// => "red"

Installation

npm install humane_list