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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@openagenda/bs-templates

v2.6.4

Published

openagenda bootstrap templates

Downloads

640

Readme

Overview

Mock project for openagenda.com styles

yarn
yarn start

Conventions

Info and secondary text

Explanatory text under a label, a radio option or a section header — and the sub-message of a banner, a notice or a panel — is a .text-muted element (or keeps the colour of its surroundings) at the inherited size:

<div className="text-muted">{info}</div>

Do not make it smaller: no <small>, no .small, no font-size set inline or in a stylesheet (style={{ fontSize: 13 }}). Everything in these interfaces — body text, control labels, accordion titles and their subtitles — sits at one size, and <small> is a relative 85% of whatever it lands in (a fixed size is no better), so a hint dressed that way reads as a different, smaller register than every other hint on the same screen. Set it apart with its colour, its place and the spacing around it, not its size. Components/RadioField.js (an option's info) and the form builder's accordion headers are the reference renderings.

<small> is left for the rare note that is genuinely subordinate to the control it sits under — a disabled state explaining itself, for instance — and not for the ordinary description of a field or an option.