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

picker-component

v2.0.1

Published

A flexible component to use where you might use a `<select>`

Readme

picker-component

A flexible component to use where you might use a <select>

Built with fastn.js

Usage

Settings

{
    options: array or object of options
    value: optional, any type
    multiple: boolean, optional, default false

    pickValue: optional, function(item){ // A function to pick a "value" for each item, to match it against the pickers "value"
        return anything

        eg:

        return item.id
    },

    itemTemplate: function(model, scope, select, renderItem){ // A template function for rendering items in the pick list
        var item = renderItem(model.get('item.something'));

        item.on('click', select);

        return item;
    },

    currentTemplate: function(model){ // A template function for rendering the currently selected value
        var selectedValue = model.get('item.something');
        return crel('div', selectedValue ? 'You picked ' + model.get('item.something') : 'Pick a value');
    },

    class: optional, string or array of strings
}

Standalone

// Create the picker
var picker = createPicker({
        options: ['foo', 'bar', 'baz']
    });

// Watch for changes to the picker's value
picker.value.on('change', function(value){
    console.log(value);
});

// Put the picker's element somewhere in the DOM.
document.body.appendChild(picker.element);

Fastn component

var fastn = require('fastn')({
    ... other components...
    picker: require('picker-component/pickerComponent')
});

var picker = fastn('picker', { options... });

Inserting

someDomNode.appendChild(picker.element);

Properties

The below properties are getter/setters, and event emitters.

  • options
  • value
  • multiple

Example usage of value property:

// retrieve value
picker.value(); // returns value

// set value
picker.value(newValue); -// returns picker.value property

// watch for changes
picker.value.on('change', function(value){
    // Do something
});

Developing

npm i

npm start

Then open http://localhost:8080

Major changes

v2: No longer emits change event when updating the components "value" progmatically. More alligned to how native web elements work.