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

weaky

v0.1.6

Published

An easy way to avoid leaks

Readme

weaky

Social Media Photo by Igor Dresjan A.P. on Unsplash

An easy way to avoid leaks.

Example

import { signal, effect } from 'https://esm.run/@preact/signals';
import { proxy, deref } from 'https://esm.run/weaky';

const fr = new FinalizationRegistry(cleanup => {
  console.log('cleaning up the effect');
  cleanup();
});

function Button(value) {
  const counter = signal(value);

  const button = Object.assign(
    document.createElement('button'),
    { onclick() { counter.value++ } }
  );

  // avoid retaining the `node` reference within the effect
  // because it would prevent GC from collecting the button
  // because such button will be referenced as parentNode
  const node = proxy(document.createTextNode(''));

  // use deref(proxy(value)) to get the original value
  button.append(deref(node));

  // cleanup the effect when the button is removed from the DOM
  fr.register(button, effect(() => {
    // forward operations to the internal reference
    // if that's still alive
    node.data = counter.value;
  }));

  return button;
}

// test one or thousand components
let [zero, one, two] = [Button(0), Button(1), Button(2)];
document.body.append(zero, one, two);

// test cleanup in a second (requires GC to kick in)
setTimeout(() => { one = one.remove() }, 1000);