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

idsplit

v0.0.1

Published

Split HTML into a minimal map from ids, for nice change detection

Downloads

3

Readme

Split some HTML into a map from ids (when present) to the the HTML associated with that id. When nested, replace the element with a reference, so there's no redundancy in the map.

This makes it fast (linear time) and straightforward to find changes to an HTML document, as long as:

  1. ids are fairly stable, and
  2. sections of the document without ids are fairly small.

When those assumptions are violated, this wont be very efficient, since it will consider very large sections of the document changed.

Specifically:

  • for each update to the document
    • run idsplit() on it
    • run idsplit.changes() to compare to previous split output
    • The "update" field of the changes will be a list of the ids of the elements to replace