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

@webring-kit/next

v0.1.1

Published

Next.js helpers for Webring Kit.

Readme

@webring-kit/next

Next.js helpers for Webring Kit.

This package is a small integration layer for using Webring Kit in Next.js applications. It keeps the browser-only Web Component loading explicit so that Server Components do not accidentally evaluate HTMLElement, customElements, or other browser-only APIs.

Install

pnpm add @webring-kit/next @webring-kit/element
npm install @webring-kit/next @webring-kit/element

Next.js, React, and React DOM are peer dependencies and must be provided by the consuming app.

Recommended Client Component pattern

"use client";

import { useEffect } from "react";

export function WebringClient() {
  useEffect(() => {
    void import("@webring-kit/element");
  }, []);

  return (
    <webring-nav
      src="/rings/example.json"
      site="https://alice.example.com"
      random="true"
    />
  );
}

Then use it from a page or layout:

import { WebringClient } from "./webring-client";

export default function Page() {
  return (
    <main>
      <h1>My site</h1>
      <WebringClient />
    </main>
  );
}

Script helper pattern

If this package exposes a script helper in your version, use it from a layout to load the browser bundle after the page becomes interactive.

import { WebringScript } from "@webring-kit/next";

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html lang="en">
      <body>
        {children}
        <WebringScript />
      </body>
    </html>
  );
}

SSR warning

Do not import @webring-kit/element from a Next.js Server Component. Load it from a Client Component, dynamic import, or script helper.

Related packages

  • @webring-kit/element for browser custom elements.
  • @webring-kit/react for React wrappers.
  • @webring-kit/core for non-UI logic.