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

chatbot-gooup1

v1.0.6

Published

A customizable React chatbot component with SCSS styling, speech recognition, and API integration

Readme

gooup1-chatbot 🤖

First, I will briefly introduce this library.

This library is created for learning purposes, written in ReactJS.
(I would have used NextJS but it had a bug... and honestly, I was too lazy to fix it 😅)


🔧 Props you can customize

  • LogoIcon
  • ChatbotIcon
  • Title
  • TitleColor
  • TitleBgColor
  • HolderInputText
  • BadgeNumber
  • BgColor
  • BgMaskColor
  • BgOpacity
  • BgMaskImg
  • MainColor
  • SubColor
  • AudioShow
  • initialMessages
  • apiEndpoint

Oh, there are quite a few variables you don't need to care about.
The main ones include:
LogoIcon, ChatbotIcon, Title, initialMessages, and apiEndpoint.


🧠 Explanation

initialMessages

This will be the default assigned conversation.

For example:

initialMessages={[
  { role: "assistant", content: "Hello! My name is MyBot!" },
  { role: "user", content: "Hi" },
  { role: "assistant", content: "How can I help you!" },
]}

With apiEndpoint, you can pass the API path directly. But there is one note, the default output structure will be as follows:
const customApiCall = async (message) => {
    const updatedMessages = [...messages, { role: "user", content: message }];

    try {
      const timestamp = Date.now();

      const result = await fetch(
        apiEndpoint,
        {
                  method: "POST",
                  headers: { "Content-Type": "application/json" },
                  body: JSON.stringify({ chatInput: updatedMessages, sessionId: timestamp }),
        }
        );

              if (!result.ok) {
                const errorData = await result.json();
                throw new Error(errorData.error || "API request failed");
        }

              const data = await result.json();
              const response = data?.output || "🤖 No respond";
              // console.log("Response_GooUp1: ", response);
              return response;
    } catch (error) {
        console.error("Error calling API:", error);
              return `🤖 Error: ${error.message}`;
    }
};

This project still has many shortcomings, but I will try to change it in the future. Thanks!