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

@pixie-cheeks/dropdown-menu

v1.0.0

Published

A reusable dropdown menu for the web

Downloads

2

Readme

About the Project

This is an npm package made for creating reusable dropdowns. It supports both hover and click events as a trigger.

This was done for an assignment by The Odin Project. Initially had the idea of implementing positioning and elaborate behavioral patterns for the dropdown menus but decided to stop when I realized I was spending way too much time on a simple task. Therefore, this code does the bare minimum of what was required.

I'm still unsure about a lot of things but I did learn a lot as well.

Getting Started

To install with npm, use the following command:

npm install @pixie-cheeks/dropdown-menu

Usage

const createDropdownManager = require('@pixie-cheeks/dropdown-menu');

const manager = createDropdownManager('dropdown__menu--hidden');

Import the createDropdownManager factory function and then use it to create a new dropdown manager. The factory function needs an invisibility class that will be toggled off and on whenever triggered. The following code explains this clearly.

.dropdown__menu--hidden {
  display: none;
}

It is assumed that the menu is hidden by default and hence the name invisibility class.

<div class="dropdown js-one">
  <button class="dropdown__trigger button">
    Click here <i class="bx bxs-down-arrow"></i>
  </button>

  <div class="dropdown__menu dropdown__menu--hidden">
    <button class="dropdown__item">Edit</button>
    <button class="dropdown__item">Copy</button>
    <button class="dropdown__item">Delete</button>
  </div>
</div>

The trigger in this case is the .dropdown__trigger element, and the .dropdown__menu is the menu. We'll use a click event for this scenario:

manager.addDropdown(
  document.querySelector('.dropdown__trigger'),
  document.querySelector('.dropdown__menu'),
  'click',
);

This will make it so every time we click on the trigger, the dropdown menu's visibility is toggled.

Removing Dropdowns

Once you are done with it, you can disable the dropdown behavior with this method:

manager.removeDropdown(
  document.querySelector('.dropdown__trigger'),
  document.querySelector('.dropdown__menu'),
  'click',
);

Contributing

If you have a suggestion that would improve this package, feel free o fork the repo and create a pull request. You can also open an issue with the tag "enhancement".

  1. Fork the Project
  2. Create a new Branch (git checkout -b improvement)
  3. Commit your Changes (git commit -m 'Optimize suboptimal code')
  4. Push to the Branch (git push origin improvement)
  5. Open a Pull Request

License

Distributed under the ISC License. See their page for more information

Acknowledgements