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

@commentasaurus/commentasaurus

v0.1.1

Published

A Docusaurus plugin that adds comments

Readme

Commentasaurus

Inline feedback, made simple

Documentation License: MIT Made with Go Made with Docusaurus


Abstract

Commentasaurus is a plugin for Docusaurus that enables inline comments within your documentation pages, letting users give direct feedback on specific sections of text, similar to Google Docs.


Tech Stack

| Layer | Technologies | Description | | ------------ | ------------------------------------------------ | ------------------------------------------------------------------------------- | | Frontend | Docusaurus, TypeScript | Renders the documentation and plugin interface | | Backend | Go | Handles comment APIs and authentication | | Storage | GitHub Discussions | Comments are stored using GitHub Discussions for collaboration and transparency |


Getting Started

Folder Structure

.
├── backend/
│   ├── main.go               # Golang API entrypoint
│   ├── routes/               # HTTP handlers and routing
│   └── ...
│
├── documentation/
│   ├── docs/                 # Markdown documentation about the plugin
│   ├── docusaurus.config.ts  # Docusaurus config (plugin settings live here)
│   └── plugins/
│       └── commentasaurus/   # Local path to test the plugin inside Docusaurus
│
└── plugin/
    └── src/                  # Source code of the plugin to be published to npm

The /plugin directory should mirror the version under /documentation/plugins/commentasaurus to ensure consistency when testing.

Running Locally

Backend (Go API)

cd backend
go run ./cmd/server/main.go

By default, the API runs on http://localhost:8080

There is also a Dockerfile that can be used

Documentation site

cd documentation
npm install
npm run start

This will open http://localhost:3000 for you.

Environment Variables

DOCKER_TAG=< Where the docker image should be uploaded to>

GITHUB_TOKEN=< GitHub token required for allowing unauthenticated users > OAUTH_ClIENT_ID=< Client ID of GitHub OAuth App > OAUTH_SECRET=< Secret from GitHub OAuth App > JWT_SECRET=< Random long string > COOKIE_KEY=< 32bit str for cookie encryption >

See the example Docusaurus config for setting up the plugin.

Preview

TODO

Contributing

I welcome contributions! Please open issues, submit pull requests, or reach out with suggestions.

  1. Fork the repo
  2. Create your branch (git checkout -b feature/thing)
  3. Commit your changes (git commit -am 'Add thing')
  4. Push to the branch (git push origin feature/thing)
  5. Open a pull request

License

This project is licensed under the MIT License. See LICENSE for details. While not required by the license, contributions back to this repository for any fixes or improvements are greatly appreciated.

Collaborators