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

previewify

v1.0.4

Published

Preview an application

Downloads

11

Readme

previewify stability

npm version build status downloads js-standard-style

When building applications you usually create a set of stateful components. For example a button can be clicked, disabled, have different types of text on it and more. If you're not testing all states, it can be easy for regressions to pop back up. That's where preview tools become useful: they allow you to view all the states of your components and pages, so making sure all different states work as expected.

screenshot

Usage

var previewify = require('previewify')
var html = require('bel')

var p = previewify()

var button = p.component('button')
button.add('with text', function (emit) {
  return html`
    <button onclick=${emit.bind(emit, 'clicked')}>
      Hello button
    </button>
  `
})
button.add('with emoji', function (emit) {
  return html`
    <button onclick=${emit.bind(emit, 'clicked')}>
      ✌️🙆🌿
    </button>
  `
})

p.mount('body')

API

p = previewify([opts])

Create a new instance of Previewify. Takes optional arguments:

  • opts.name (default: 'previewify') set the nav header name
  • opts.url (default: '/') set the nav header url

Exposes a few internal properties:

  • p.app instance of Choo
  • p.components array of registered components

DOMElement = p.start()

Start the instance, returns a DOM tree that can be mounted on the DOM.

p.mount(node)

Start and mount the instance on the DOM. Node can either be a DOM node or a string. Replaces the selected Node.

component = p.component(name)

Create a new component with a name.

component.add(name, callback)

Add a new state of the component.

component = p.page(name)

Create a new page with a name. (To be implemented)

page.add(name, callback)

Add a new state of the page. (To be implemented)

FAQ

Why isn't this a command line tool?

Separation of concerns, this is just a UI module - use bankai or a similar compiler tool if you want to have a live reloading dev environment for your components.

Why did you build this?

I thought the React storybook stuff was neat, and wanted something similar for regular DOM elements.

See Also

  • https://storybooks.js.org
  • https://calibreapp.com/
  • http://sizzy.co/
  • https://developers.google.com/web/tools/lighthouse/

License

MIT