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

obsidium

v2.0.0

Published

A declarative wrapper for all the JS observers.

Readme

Obsidium

Declarative wrapper class for the JS observers.

Rationale

Created to encourage greater use of these high-value JS utilities, as they're vastly unknown and criminally underused, largely due to their complex implementation strategy. I found that every time I wanted to use one or more of them, I'd have to go out of my way to research and refresh my understanding thereof.

Moreover, there are subtle differences in their implementation between them that are somewhat irritating. I really just want to set it and forget it. Obsidium allows you to do just that…in a strongly typed, consolidated way.

Obs. name | wraps… --------- | -------- mutation | MutationObserver resize | ResizeObserver intersection | IntersectionObserver

Usage

The idea is to instantiate the desired type of observer, then simply subscribe to it…without having to be aware of the underlying BS.

Implementation examples (not exhaustive):

import { Obsidium } from 'obsidium';

Obsidium.mutation(scopeElement)
	.on('add', addFn)
	.on('remove', removeFn);

Obsidium.resize(element).on('resize', resizeFn);

Obsidium.intersection(element)
	.on('intersect', function ([entry]) {
		this.dump();
		// do something...
	});

See more code examples.

Members

Control your instance with the following methods:

Method | Desc. ------ | ----- suspend | stop observing; reserves the right to resume resume | resume a suspended observer toggle | suspend or resume depending on observer state dump | end the process entirely and destroy the instance

Settings

The generic default settings are set for each observer, which can be optionally overridden via the second argument of the wrapped constructor, specific to the chosen observer type. Caveat: resize has no such settings arg. as it's not complex enough to need it.

const myObs: Obsidium = Obsidium[name](element, options?);

Advanced

  • use the alternatively available subscribe method
  • find the Obsidium instance object as an additional callback parameter
  • attach multiple observers to the same element at once with Obsidia
  • import only the wrapper class you need for optimal tree shaking

Daniel K.