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

@chronocide/hyper

v0.3.2

Published

<div align="center"> <h1>@chronocide/hyper</h1> <p>Tiny DOM library</p> </div>

Readme


hyper is a tiny TypeScript library designed to ease working with the DOM. hyper tries to be as simple as possible whilst maintaining good developer experience and currently features:

  • Simple wrapper around native API's (DOM)
  • No vDOM, all state is stored within the DOM*
  • List caching

Installation

npm i @chronocide/hyper

Usage

import h from '@chronocide/hyper';

const img = h('img')({ src: '/cat.png' })(); // HTMLImageElement

document.body.appendChild(img);

List

List items can be cached using list, only updated if the data is changed; order does not matter. Data does not need to be unique, as duplicate nodes are cloned.

import type { Component } from '@chronocide/hyper';

import h, { list } from '@chronocide/hyper';

type Planet = { id: string; name: string };

const planets: Planet[] = [
  { id: 'jupiter', name: 'Jupiter' },
  { id: 'mars', name: 'Mars' },
  { id: 'pluto', name: 'Pluto' }
];

const ul = h('ul')()(); // <ul></ul>
const component: Component<Planet> = planet => h('li')()(planet.name);

const update = list<Planet>(component)(ul);
update(planets); // <ul><li>Jupiter</li><li>Mars</li><li>Pluto</li></ul>

Testing

hyper relies on the DOM, which may not always be available. In those cases, it's possible to set a custom DOM using env:

import { env } from '@chronocide/hyper';
import { JSDOM } from 'jsdom';

const dom = new JSDOM();
env.document = dom.window.document;

Examples can be found in the test files, such as hyper.spec.ts.

Development

hyper uses puppeteer for browser testing and does not install Chrome by default. To run tests, create an .env file using:

npm run env

Note: If you're running Linux, have Chrome installed in a non-standard location or wish to use a different browser, you can create the .env file yourself:

BROWSER_PATH=<path_to_browser>