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

@householdjs/ui

v2.2.0-alpha.0

Published

premade unstyled ui elements

Downloads

47

Readme

<Dropdown />

props:

   isOpen: boolean
   checkDOMUpdate?: boolean
   maxHeightDefined?: number
   children: ReactNode

props in detail:

  • isOpen
    • in most cases the only option you need to define to make this work
  • maxHeightDefined
    • detecting element.offsetHeight comes with a layout reflow expense, this option will help you prevent it
    • we might ask for the content to load on Dropdown open, in that case, we won't know the content height upfront
  • checkDOMUpdate
    • if Dropdown children are being deeply nested, the dropdown might not be able to detect changes inside dropdown - e.g adding an item to a list
    • you enable this option, and the Dropdown will detect any changes inside the Dropdown DOM. It comes at the performance expense of course.

<SvgIcon />

props:

   withPointer?: boolean
   viewBoxSize?: number - must be defined if viewBoxWidth and viewBoxHeight are not
   viewBoxWidth?: number - must be defined if viewBoxSize is not
   viewBoxHeight?: number - must be defined if viewBoxSize is not
   size?: number
   children: ReactNode

props in detail:

  • pointingTo
    • default is top, make sure your icon (e.g arrow) points to top when exported
  • withPointer
    • adds pointer to an element
  • viewBoxSize
    • you copy it from original svg element
    • never change this value!! - paths inside svg are calculations based on viewBox
    • when viewBoxWidth and viewBoxHeight are the same -> you don't have to define viewBoxWidth & viewBoxHeight then
  • viewBoxWidth
    • you copy it from original svg element
    • never change this value!! - paths inside svg are calculations based on viewBox
    • don't define it if you defined viewBoxSize
  • viewBoxHeight
    • you copy it from original svg element - never change this value!! - paths inside svg are calculations based on viewBox
    • don't define it if you defined viewBoxSize
  • size
    • if not defined, it takes (viewBoxWidth && viewBoxHeight) || viewBoxSize as it's width and height parameters
    • if width and height are not the same, it defines the longer side length -> the other side is ratio calculated
  • children
    • all other svg elements but <svg />