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 🙏

© 2025 – Pkg Stats / Ryan Hefner

paintor

v1.4.6

Published

100% JavaScript view library for the browser and for the server

Downloads

283

Readme

Paintor

Static Badge Static Badge

npm version npm package minimized gzipped size npm downloads npm type definitions test license

A JavaScript library for building reactive client-side user interfaces or HTML code.

Documentation and Examples

Key Features

  • JavaScript: The code you write is the code to run
  • Zero dependencies
  • Reactive: Through Proxy and DOM events
  • Templates in JavaScript or HTML: JavaScript HTML-like tree structure (HyperScript) or HTML syntax in template literals
  • Observers: Receive events on state changes
  • SSR: Generate HTML code on the server
  • Internationalization (i18n)
  • Type Definitions: Built-in TypeScript definitions for code completion and type safety

Quick Example

import { component, state, template, on } from 'paintor'

// Use a global state
const globalState = state({ clicks: 0 })

// Create a template
const myTemplate = template((tags) => {
  const { div, button, html } = tags

  // Or, use a local state
  const localState = state({ clicks: 0 })

  // Build JavaScript template
  div(
    button(
      {
        class: 'buttons',
        onClick: () => globalState.clicks++
      },
      'Click me'
    ),
    div(() => globalState.clicks)
  )

  // Or, build HTML template in a string
  html`
    <div>
      <button class="buttons" onClick=${() => localState.clicks++}>
        Click me
      </button>
      <div>${() => localState.clicks}</div>
    </div>
  `
})

// Create a component, using the template
const app = component(myTemplate)

// Render the component
app.paint('#app')

// Or, generate HTML string
const htmlCode = app.html()

// Observe state changes if you want
on(globalState.clicks).change((event) => {
  console.log(`Clicked ${event.value} times`)
})

Why?

Cults? No.

I don't like React. As a JavaScript developer, every time I was curious enough to see and understand what React offers, I was disgusted. I couldn't stand looking at React code for more than a few minutes. There is something in it that is not intuitive for me. I think the learning curve of React is too steep for the problems it aims to solve. To the point that everyone who manages to endure the learning process, eventually becomes a cult follower. This is how I think about Angular and other over-hyped, but complex solutions.

"Aha" and "Wow"

I much prefer Vue or Svelte, which at the time I first stared hearing about React were probably less popular than Angular. But when I looked at them, I quickly had this "aha" moment, and for me Svelte even has that "wow" factor. For me, the quick "aha" and the "wow" are very important.

To transpile? How about No?

However, I'm not a big fan of the idea to write something in a non-native format and transpile it on every small change in order to use it. This is usually a deal-breaker for me.

Vanilla

Then I was inspired by Mithril, which is fairly easy to understand and vanilla, although it doesn't really have the "wow" factor. As I often do in such cases, I decided to quickly write something like it, tailored for my needs. Well, this took some years and it's still an ongoing process.