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/client

v0.6.1

Published

The browser-side [PageLoop](https://github.com/rw3iss/pageloop) SDK — the `PageLoop` class plus thin React / Preact / Solid wrappers. Framework-agnostic at its core; UI rendering goes through a `UIRenderer` you supply.

Readme

@pageloop/client

The browser-side PageLoop SDK — the PageLoop class plus thin React / Preact / Solid wrappers. Framework-agnostic at its core; UI rendering goes through a UIRenderer you supply.

Install

The framework wrappers (/react, /preact, /solid) render via the vanilla DOM renderer, which they lazy-load at runtime with import('@pageloop/vanilla'). So if you import any framework subpath you must also install @pageloop/vanilla alongside this package:

pnpm add @pageloop/client @pageloop/vanilla react

Swap react for preact or solid-js (each is an optional peer dependency). For the headless . entry, neither a framework nor @pageloop/vanilla is required — you bring your own UIRenderer.

Exports

| Subpath | Use when | |---|---| | . | Headless core: the PageLoop class, ApiClient, PageTracker, CommentEngine, the UIRenderer interface. You instantiate it directly and bring a renderer. | | /react | React <PageLoopProvider> + hooks. Optional peer react. | | /preact | Preact <PageLoopProvider> + hooks. Optional peer preact. | | /solid | Solid <PageLoopProvider> + signal hooks. Optional peer solid-js; ships preserved JSX. | | /react/style.css, /preact/style.css, /solid/style.css | The renderer stylesheet. Import once at the app root. |

. — headless core

You own the lifecycle and pass a UIRenderer (e.g. VanillaRenderer from @pageloop/vanilla, or your own implementation):

import { PageLoop } from '@pageloop/client';
import { VanillaRenderer } from '@pageloop/vanilla';
import '@pageloop/vanilla/style.css';

const pageloop = new PageLoop(
  { endpoint: 'https://your-pageloop-server.com', projectId: 'your-slug' },
  { renderer: new VanillaRenderer() },
);
await pageloop.start();

/react, /preact

Wrap your tree once; the renderer paints the floating UI into document.body, and the hooks expose its reactive state (usePageLoop, useComments, usePage, useUser, useRole, useConnected, useReplies, useReactions):

import { PageLoopProvider, useComments } from '@pageloop/client/react';
import '@pageloop/client/react/style.css';

function App() {
  return (
    <PageLoopProvider config={{ endpoint, projectId }}>
      <Comments />
    </PageLoopProvider>
  );
}

function Comments() {
  const comments = useComments(); // re-renders as the bus broadcasts
  return <span>{comments.length} comments on this page</span>;
}

Preact is identical — import from @pageloop/client/preact (and its style.css).

/solid

Same provider, but hooks return Solid Accessor<T> signals (usePageLoop, createReplies, createReactions):

import { PageLoopProvider, usePageLoop } from '@pageloop/client/solid';
import '@pageloop/client/solid/style.css';

function App() {
  return (
    <PageLoopProvider config={{ endpoint, projectId }}>
      <Status />
    </PageLoopProvider>
  );
}

function Status() {
  const { connected } = usePageLoop();
  return <span>{connected() ? 'live' : 'offline'}</span>;
}