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

dom-callcount

v2.0.1

Published

Track callcount of dom apis. Useful for vdom-testing.

Downloads

10

Readme

DOM CallCount

dom-callcount is a tiny library to track calls to the DOM. The main use case is for developers of virtual-dom libraries which want to minimize dom operations as much as possible.

If you're testing in a real browser you should use a MutationObserver instead. This library is mainly for environments where MutationObserver is not available, because the latter is quite hard to polyfill.

This library is heavily inspired by these utils from ivi.

Installation

# npm
npm install --save-dev dom-callcount

# yarn
yarn add --dev dom-callcount

Usage

Under the hood it works by spying on the prototype of Node and Document. After the callback is called, these are restored to their previous state and all spies are removed.

import observe from "dom-callcount";

const result = observe(() => {
  const div = document.createElement("div");
  const text = document.createTextNode("foo");
  div.appendChild(text);
});

console.log(result);
// Logs:
// {
//   createElement: 1,
//   createTextNode: 1,
//   appendChild: 1,
// }

License

MIT, see License.