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

thenothing

v0.0.3

Published

The Nothing

Downloads

6

Readme

The Nothing

POC of a back-to-the-roots idea of building a website by writing crude HTML code with native attributes for event handlers like onmouseover="" or onsubmit="". There are no built-in abstractions for dom nodes, events or styling. What you write in your component renderer in ES6 is what you will get in DOM. It's similar to web components.

The POC library in nothing.js only takes 50 lines of code and consists of State, makeCallback and makeIterator(for lists). There's no build step and there are no dependencies.

Basic component with state

const Header = function (parent) {
  const state = new State({ title: 'Default component title', parent })
  state.render = () => `<h1 style="color: #aaa;">${state.title}</h1>`
  return state.getUpdater()
}

Composition

const App = function (parent) {
  const state = new State({ parent })
  // Due to no preprocessing each component must be instantiated before being used in render(),
  // here the default options before loading dynamic content can be set
  const header = Header({ title: 'Default app title' })
  state.render = () => {
    // This part gets executed on every rerender
    return `<div>
      ${header({ title: 'Dynamic title' })}
    </div>`
  }
  return state.getUpdater()
}

Event handlers

In todo.js you'll find the below TodoItem component. onclick is a regular HTML attribute

const TodoItem = function () {
  const state = new State({ caption: '' })
  state.render = () => `<li>
    ${state.caption}
    <button id="${state.id}" onclick="${state.remove}">Done</button>
  </li>`
  return state.getUpdater()
}

state.remove is a pointer to a callback passed by the parent. makeCallback is the crucial function exporting a local handler so it can be accessed by the resulting HTML with it's native handler declaration attribute

const remove = makeCallback((event) => {
  state.set('items', state.items.filter(item => item.id !== event.target.getAttribute('id')))
})

Demo

Clone this repo and run npm start

Or visit The demo using the files listed below alternatively editable JSFiddle demo

Files

  • index.html - the starting point
  • nothing.js - the engine
  • todo.js - the app