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 🙏

© 2025 – Pkg Stats / Ryan Hefner

ember-select-list

v0.9.6-rc.1

Published

A basic replacement for the old ember select view, which strives to follow modern ember conventions.

Downloads

1,215

Readme

ember-select-list

ember-select-list is a basic <select> component which strives to replace the old {{view 'select'}} while following the modern ember paradigm of "data-down-actions-up" as closely as possible.

Demo

http://begedin.github.io/ember-select-list

Installation

  • ember install ember-select-list

Using the addon

A straight replacement of the old select view would be done in the following way.

The following handlebars markup

{{view "select"
       content=programmers
       optionValuePath="content.id"
       optionLabelPath="content.firstName"
       value=selectedProgrammerId}}

can be replaced with

  {{select-list content=programmers
                optionValuePath='id'
                optionLabelPath='firstName'
                value=selectedProgrammerId
                action=(action (mut selectedProgrammerId))}}

As clear from the markup, the default behavior of the value binding is one way. In order to make it two-way, using the mut helper is required. Additionally, label and value paths do not require speficying the root element name.

Using attribute bindings

The following attribute bindings are supported: disabled, tabindex, required, title

Nesting is supported

The following syntax for label and value paths is supported and will work.

{{select-list content=myData
              optionValuePath='level1.level2.id'
              optionLabelPath='level1.level2.label'}}

Not specifying a value or label path will work

This will work

{{select-list content=myData
              optionLabelPath='level1.level2.label'}}

As will this

{{select-list content=myData
              optionValuePath='level1.level2.id'}}

The corresponding component property will simply be set to the value of the entire selected item in the content array.

You can use it with a collection of simple strings, or complex objects.

content can be int he format of ['Item A', 'Item B', ...] or [ ObjectA, ObjectB, ...].

Instead of using mut, you can bind it to any action you want

  {{select-list content=myData
                action='myCustomAction'}}

The action will be triggered when the selection is changed.

Ember support

This addon should currently work with [email protected], but I haven't tested it.