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

@edux-design/comments

v0.1.4

Published

Structured comment block for discussion threads, with avatar, metadata, actions, and nested replies.

Readme

@edux-design/comments

Structured comment block for discussion threads, with avatar, metadata, actions, and nested replies.

Install

npm i @edux-design/comments @edux-design/avatars

Usage

import { Comment } from "@edux-design/comments";
import { CommentComposer } from "@edux-design/comments";
import { CommentMention } from "@edux-design/comments";

export function Example() {
  const [resolved, setResolved] = React.useState(false);

  return (
    <Comment
      author="Alex Johnson"
      timestamp="2h ago"
      body="Left a few notes on the introduction. Let me know if you want me to draft the edits."
      avatarProps={{ name: "Alex Johnson" }}
      resolved={resolved}
      onResolve={() => setResolved((prev) => !prev)}
      replies={
        <Comment
          author="Taylor"
          timestamp="1h ago"
          body="Happy to take the edits."
          avatarProps={{ name: "Taylor" }}
          variant="resolved"
        />
      }
    >
      <Comment.Actions>
        <Comment.Reply />
        <Comment.Edit />
        <Comment.Resolve />
      </Comment.Actions>
    </Comment>
  );
}
export function ComposerExample() {
  const [value, setValue] = React.useState("");
  const [query, setQuery] = React.useState("");

  return (
    <CommentComposer
      value={value}
      onChange={(event) => setValue(event.target.value)}
      onSubmit={() => setValue("")}
      onCancel={() => setValue("")}
      avatarProps={{ name: "Alex Johnson" }}
    >
      <CommentMention
        peopleList={[
          { id: "alex", name: "Alex Johnson", handle: "alex" },
          { id: "priya", name: "Priya Singh", handle: "priya" },
        ]}
        onQueryChange={setQuery}
      />
      <div className="mt-8 text-xs text-fg-subtle">
        Mention query: <span className="font-semibold">{query || "—"}</span>
      </div>
    </CommentComposer>
  );
}

Mentions

CommentMention handles the in-editor mention menu and emits the active query via onQueryChange when the user types @query at the cursor. Debounce behavior is left to the consumer.

import { CommentComposer, CommentMention } from "@edux-design/comments";

<CommentComposer value={value} onChange={(event) => setValue(event.target.value)}>
  <CommentMention peopleList={people} onQueryChange={setQuery} />
</CommentComposer>;

Resolve / Re-open

Comment.Resolve swaps label and styling based on the resolved state. You can override the label if needed.

<Comment resolved={isResolved} onResolve={toggleResolved}>
  <Comment.Actions>
    <Comment.Resolve />
    <Comment.Resolve label="Re-open thread" />
  </Comment.Actions>
</Comment>