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

dompack-pulldown

v0.1.0

Published

Dompack Pulldown

Downloads

3

Readme

dompack pulldown

Yet another pulldown. The dompack pulldown differs from a lot of other select replacements in that it can resize itself according to the size of the items in the pulldown, just like the original <select>. Most other replacements are either fixed width or rely on javascript to properly size themselves.

dompack-select observes the replaced <select> element and will automatically update its contents if the select is modified, and pick up any change to the value or selectedIndex property

dompack pulldown relies on dompack and SCSS, and leaves the choice of used classnames (except for a few internal classes you should never modify) to you.

Feature shortlist

  • Clean ES6/7 (Babel) and SCSS setup
  • Automatically resize the select control based on the content of the options
  • Native HTML5 events
  • Automatically picks up changes made to the original DOM select and applies it to the replaced control
  • Supports responsive fallback to browser-native controls

To integrate into your project:

Select a class, eg 'mypulldown', to use for your pulldowns. You can set up different pulldowns using different classes. The example below simply takes over all <select> controls:

The JavaScript part:

import * as dompack from "dompack";
import Pulldown from "dompack-pulldown";

dompack.register('select', node => new Pulldown(node, 'mypulldown'));

The SCSS part, assuming you want each pulldown control and each item to be exactly 28px in height:

@import "~dompack-pulldown/styles/mixins";

.mypulldown
{
  @include dompack-pulldown(28px);
}

Responsive disabling

You may want to disable this control on mobile devices. You could simply not invoke dompack.register on such devices, or use a media query to show/hide the original and new controls, eg:

.mypulldown
{
  display:none; //By default, hide us
}
@media (min-width: 481px) // <=480px - native pulldown. >480px - replaced pulldown
{
  .mypulldown
  {
    @include dompack-pulldown(28px);
  }
}

Common issues

  • The control takes up vertical space for all the items, even if closed

Make sure you specified a height for the control itself.