npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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 🙏

© 2020 – Pkg Stats / Ryan Hefner




Functional approach to authoring performant HTML components using plugins





npm version build status downloads style

A functional approach to authoring performant HTML components using plugins. Syntactic suggar on top of nanocomponent. Pass in a function and get another function back that handles rerendering as needed when called upon.


The most straightforward use is to pass in a function and have the default shallow diff figure out whether to rerender the component on consecutive calls.

// button.js
const html = require('bel')
const component = require('fun-component')

module.exports = component(function button (ctx, clicks, onclick) {
  return html`
    <button onclick=${onclick}>
      Clicked ${clicks} times
// app.js
const choo = require('choo')
const html = require('choo/html')
const button = require('./button')

const app = choo()
app.route('/', view)

function view (state, emit) {
  return html`
      ${button(state.clicks, () => emit('click'))}

app.use(function (state, emitter) {
  state.clicks = 0
  emitter.on('click', () => {
    state.clicks += 1


Though fun-component was authored with choo in mind it works just as well standalone!

const button = require('./button')

let clicks = 0
function onclick () {
  clicks += 1
  button(clicks, onclick)

document.body.appendChild(button(clicks, onclick))



component(name<string>, render<function>)

Create a new component context. Either takes a function as an only argument or a name and a function. Returns a function that renders the element. If no name is supplied the name is derrived from the functions name property.

Warning: implicit function names are most probably mangled during minification. If name consistency is important to your implementation, use the explicit name syntax.

component('hello', () => html`<h1>Hi there!</h1>`)


The component context (ctx) is prefixed to the arguments of all lifecycle hooks and the render function itself. The context object can be used to access the underlying nanocomponent instance.

// Exposing nanocomponent inner workings
component(function echo(ctx) {
  return html`<h1>I'm ${ctx._name} on the ${ctx._hasWindow ? 'client' : 'server'}</h1>`


All the lifecycle hooks of nanocomponent are supported, i.e. beforerender, load, unload, afterupdate, and afterreorder. Lifecycle hooks are declared on the element itself (with an "on" prefix) and are forwarded to the underlying nanocomponent instance.

All lifecycle hooks are called with the context object and the latest arguments used to call the component.


fun-component comes with a baked in default update function that performs a shallow diff of arguments to determine whether to update the component. Setting onupdate on the element overrides this default behavior.

onupdate(ctx<object>, args<array>, prev<array>)

Opposed to how nanocomponent calls the update function to detemrine whether to rerender the component, fun-component not only supplies the next arguments but also the previous arguments. These two can then be compared to determine whether to update.

Tip: Using ES2015 deconstruction makes this a breeze.

component(function greeting(ctx, title) {
  return html`<h1 onupdate=${update}>Hello ${title}!</h1>`

// Deconstruct arguments and compare `title`
function update(ctx, [next], [prev]) {
  return next !== prev


Using every lifecycle hook available. The rendered element can be accessed on the context object as ctx.element.

component(function hooks(ctx, title) {
  return html`
    <div onupdate=${update} onbeforerender=${beforerender} onload=${load} onunload=${unload} onafterupdate=${afterupdate} onafterreorder=${afterreorder}>
      Hello ${title}!

function update(ctx, [title], [prev]) {
  console.log(`diffing ${title} and ${prev}`)
  return title !== prev

function beforerender(ctx, title) {
  console.log(`will render with ${title}`)

function load(ctx, title) {
  console.log(ctx.element, `mounted in DOM with ${title}`)

function unload(ctx, title) {
  console.log(ctx.element, `removed from DOM with ${title}`)

function afterupdate(ctx, title) {
  console.log(`updated with ${title}`)

function afterreorder(ctx, title) {
  console.log(`reordered with ${title}`)


Plugins are middleware functions that are called just before the component is rendered or updated. A plugin can inspect the arguments, modify the context object or even return another context object that is to be used for rendering the component.

const html = require('bel')
const component = require('fun-component')

const greeter = component(function greeting(ctx, title) {
  return html`<h1>Hello ${title}!</h1>`

greeter.use(function log(ctx, title) {
  console.log(`Rendering ${ctx._ncID} with ${title}`)
  return ctx


fun-component is bundled with with a handfull of plugins that cover the most common scenarios. Have you written a plugin you want featured in this list? Fork, add, and make a pull request!

  • spawn – Spawn component contexts on demand and discard on unload.
  • restate – Add state object and state management to the context object.
  • logger – Add a logger (using nanologger) to the context object.
  • cache – Cache element and reuse on consecutive mounts.


For example implementations, see /examples. Either spin them up locally or visit the link.

Why tho?

Authoring a component should be as easy as writing a function. Using arguments and scope to handle state is both implicit and transparent. Worrying about calling context, and stashing things on this makes for cognitive overhead.

Not for you? If object oriented programming is your thing, use nanocomponent. If you're more into events, maybe microcomponent is a good fit.

See Also