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

@pageloop/loader

v0.6.1

Published

A tiny (~2 KB gz) auto-updating loader shim for the [PageLoop](https://github.com/rw3iss/pageloop) widget. You embed **this** one small script; on every page load it fetches the current widget bundle's manifest from your server, injects the right JS + CSS

Readme

@pageloop/loader

A tiny (~2 KB gz) auto-updating loader shim for the PageLoop widget. You embed this one small script; on every page load it fetches the current widget bundle's manifest from your server, injects the right JS + CSS, and calls PageLoop.init() for you. If a new bundle ever fails to boot, it silently rolls back to the last-known-good version — so embedders never re-paste a tag to stay current.

This is the recommended script-tag install for sites whose HTML you can edit. It's served by your PageLoop server, so you don't install it from npm — you point a <script> at it.

Integrate (in your page <head>)

<script
  src="https://your-pageloop-server.com/cdn/loader/pageloop-loader.js"
  data-project="your-project-slug"
  data-endpoint="https://your-pageloop-server.com"
  data-channel="latest"
  async
></script>

That's it — the toolbar appears on load and users sign in from it. The loader injects the widget's CSS too, so there's no separate stylesheet to add.

Attributes

| attribute | required | notes | |---|---|---| | data-project | ✓ | Your project slug (from the project dashboard). | | data-endpoint | ✓ | Your PageLoop server origin. | | data-channel | | Update track. latest (default) = newest release; 0.3 = patch-only on that minor; 0.3.1 = pinned exact version. | | async | | Recommended — the loader is DOM-ready-safe and won't block paint. |

How updates work

The loader reads <endpoint>/cdn/<channel>/manifest.json, injects the published bundle (ESM with dynamic-import chunks where supported, else the UMD fallback), and boots it. On any failure (manifest 404, script load error, init throw) it falls back to a lastGood bundle saved in localStorage and surfaces a toast. Diagnostics land in localStorage.pageloop.loader.lastError.

Prefer to manage the bundle version yourself or forbid the runtime fetch via CSP? Use the pinned UMD tag from @pageloop/vanilla instead — at the cost of manual updates.