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

minimui

v2.3.8

Published

Minimalist React Component Library

Downloads

18

Readme

Build Status JavaScript Style Guide

THIS IS A WORK IN PROGRESS

minimui

Minimui is my minimalist React component library that I use for various projects.

YMMV.

I have developed this React component library to standardise form components, create custom components, support standardised states, and do this all in a visually attractive way.

Principles

  • Native components SHOULD be used where possible, as this is necessary to avoid problems that lie outside the browser canvas. For example, using a <select> with options that overflow over the bottom of the browser window is problematic as they will not be displayed, whereas a native control will render the options upwards and viewable.
  • All form components MUST support "focus", "error", "disabled" and "in-progress" states.
  • All form components MUST support keyboard navigation (tab), and keyboard activation where applicable (spacebar).
  • All component states MUST be observable to colour-blind people and when rendering is grayscale, i.e. no component state is primarily indicated by colour, but colours are used as a secondary aesthetic state indicators.
  • All form components MUST support "in-progress" state when an asynchronous action has been triggered (e.g. an XHR).
  • Components that are in a "disabled" or "in-progress" state MUST NOT emit events (e.g. onClick).
  • All form components MUST be controlled components.

Dependencies

  • react 16.x
  • font-awesome 5.x
  • styled-components 4.x