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

comment-mode

v0.2.2

Published

embeddable commenting for live prototypes

Downloads

1,235

Readme

comment mode

Embeddable commenting for live prototypes (Next.js / React).

Install

npm install comment-mode

Minimal setup

The fastest way to get started is the Commentator wrapper. It wires up the provider, commentable surface, and overlay for you.

import { Commentator } from "comment-mode";

function App() {
  return (
    <Commentator
      config={{
        projectSlug: "my-prototype",
        surfaceId: window.location.pathname,
        github: {
          owner: "your-github-user-or-org",
          repo: "your-repo-name",
        },
      }}
    >
      {/* Your prototype UI. Clicks here create comment pins when comment mode is on. */}
    </Commentator>
  );
}

Example: Next.js app layout

Here’s a more complete example that mirrors the prototype demo, including a surfaceId based on pathname + search params and a custom API base URL.

import React from "react";
import { usePathname, useSearchParams } from "next/navigation";
import { Commentator } from "comment-mode";


export function CommentatorLayout({ children }: { children: React.ReactNode }) {
  const pathname = usePathname();
  const searchParams = useSearchParams();
  const surfaceId = [
    pathname ?? "/",
    searchParams?.toString() ? `?${searchParams.toString()}` : "",
  ].join("");

  return (
    <Commentator
      config={{
        projectSlug: "my-prototype",
        surfaceId,
        github: {
          owner: "your-github-user-or-org",
          repo: "your-repo-name",
        },
      }}
      position="right"
      surfaceClassName="min-h-screen flex flex-col"
    >
      {children}
    </Commentator>
  );
}

Required config

  • projectSlug (required) — Identifies your project (e.g. "my-prototype").
  • surfaceId (required) — Identifies the page/screen/surface (e.g. window.location.pathname or pathname + search).

Optional extras

  • position"left" or "right" for where the comment panel appears (default "right").
  • apiBaseUrl — Override the Comment Mode API base URL (only needed if you are self‑hosting the API).
  • pageUrl — Full URL of the current page (e.g. window.location.href). Used when creating GitHub issues so the issue body can link back to the prototype.
  • github — GitHub integration for turning comment threads into issues:
    • owner (required if github is set) — GitHub org or username.
    • repo (required if github is set) — Repository name.
    • createIssueForNewThreads — When true, every new comment thread automatically creates a GitHub issue. Default is false (opt-in). When false, users can still create an issue from a thread via the thread menu (“Create GitHub issue”). When a thread already has an issue, the menu shows “Go to GitHub issue” instead.