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

docusaurus-comment-section

v2.0.0

Published

Docusaurus comment section component

Downloads

26

Readme

Docusaurus comment section plugin

Checkout DEV_README.md file to learn about how this npm package is maintained.

This is pretty straightforward npm package code. For docusaurus (but, actually, can be used for any other react project) website to have comment section. Comments are stored in firestore database.

npm package website

github

How to use

Step 1: Setting up firestore database

  1. Have Google account.
  2. Go to console.firebase.google.com and create new project (or use an existing one), create firestore database.
  3. Set security rules:
rules_version = '2';

service cloud.firestore { match /databases/{database}/documents { match /posts/{postId} { allow read: if true; allow write: if true; } match /comments/{commentId} { allow read: if true; allow create: if ( request.resource.data.postId is string && request.resource.data.content is string && request.resource.data.timestamp is timestamp ); allow update: if true; allow delete: if false; } } }
  1. Go to project settings and create an app (web app). Copy the const firebaseConfig = { ... } part.

Step 2: Use the package (basic example)

npm install docusaurus-comment-section

in your react project root dir and you're good to go.

Here's the usage example. Or just checkout the test-app/. It has the complete usage example. For the firebaseConfig part just paste the copied part from firebase project created web app.

import { CommentSection, FirebaseProvider } from "docusaurus-comment-section";

const firebaseConfig = {
  apiKey: "AIqaSyB9pUI5p93eatRFG4ZAU1g88oYACmDxXC4",
  authDomain: "abc.firebaseapp.com",
  projectId: "abc",
  storageBucket: "abc.firebasestorage.app",
  messagingSenderId: "496235222546",
  appId: "1:497425222546:web:404e256e643ff0337b44f4b",
};

function App() {
  return (
    <>
      <h1>Comments</h1>
      <FirebaseProvider config={firebaseConfig}>
        <CommentSection postId={"hohoho"} isDefaultVerified={true} />
      </FirebaseProvider>
    </>
  );
}

export default App;

Step 3: Implementing in docusaurus blog posts (example)

Of course you can use component as you like, but here is one of the possible solutions - show comment section only in the end of single page blog post display.

npm run swizzle BlogPostPage --eject

And then insert this code in src/theme/BlogPostPage/index.tsx:

      <BlogPostItem>{children}</BlogPostItem>

      {/* Added content */}
      <FirebaseProvider config={firebaseConfig}>
        <CommentSection postId={metadata.title} isDefaultVerified={true} />
      </FirebaseProvider>{" "}
      {/* End of added content */}

      {(nextItem || prevItem) && (
        <BlogPostPaginator nextItem={nextItem} prevItem={prevItem} />
      )}

Also, of course, include firebaseConfig constant in the file.

How this works

Based on the website sesinuliai.lt.

Firestore database structure:

{
  "posts": [
    {
      "postId": "AnyIdButUnique",
      "isDefaultVerified": false
    }
  ],
  "comments": [
    {
      "postId": "AnyIdButUnique",
      "content": "Required content",
      "name": "Not required name, can be anonymous",
      "isAuthor": false,
      "email": "Not required email. Not shown",
      "verified": true
    }
  ]
}

More detailed explanation later.

Future improvements

  1. Ability to easily customize style.
  2. Admin console for verifications.
  3. Ability to make replies.
  4. Informing user via email about given reply to the comment and about verification updates.