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 🙏

© 2025 – Pkg Stats / Ryan Hefner

robogpt-nodes

v1.0.13

Published

RoboGPT Node based workflow editor

Readme

Banner

robogpt-nodes

robogpt-nodes is a framework‑agnostic React component library that provides a node‑based editor for building robot workflows.
With robogpt-nodes, you can drag and drop nodes to visually create programs that your robot can execute — a simpler way to program robots using RoboGPT.

Screenshot


Installation

npm install robogpt-nodes
# or
yarn add robogpt-nodes
# or
pnpm add robogpt-nodes

Usage

"use client";

import { NodeEditor } from "robogpt-nodes";
import "robogpt-nodes/dist/index.css";

export default function Page() {
  return <NodeEditor />;
}

Features

  • Drag & Drop Node Editor – visually connect nodes to build workflows
  • Robot Programming Made Simple – create programs without writing code
  • Framework‑agnostic – works in Next.js, Vite, CRA, Remix, etc.
  • Customizable – built with Radix UI, Zustand, and Tailwind utilities

Requirements

  • React >=18
  • React DOM >=18
  • TailwindCSS (if you want to extend/customize styles)
  • A Next.js API route for publishing workflows (see below)

Workflow Publishing API (Next.js)

The NodeEditor component is designed to publish the compiled workflow to your backend.
By default, it expects a Next.js API route at /api/publish.

Example: /app/api/publish/route.ts

import Pusher from "pusher";
import { NextRequest } from "next/server";

const pusher = new Pusher({
  appId: process.env.PUSHER_APP_ID || "dummy-app-id",
  key: process.env.PUSHER_KEY || "dummy-key",
  secret: process.env.PUSHER_SECRET || "dummy-secret",
  cluster: process.env.PUSHER_CLUSTER || "mt1",
  useTLS: true,
});

export async function POST(req: NextRequest) {
  try {
    const { channel, event, payload } = await req.json();

    if (!channel || !event) {
      return new Response(
        JSON.stringify({ error: "channel and event are required" }),
        {
          status: 400,
          headers: { "Content-Type": "application/json" },
        }
      );
    }

    await pusher.trigger(channel, event, payload ?? {});

    return new Response(JSON.stringify({ ok: true }), {
      status: 200,
      headers: { "Content-Type": "application/json" },
    });
  } catch (err) {
    return new Response(
      JSON.stringify({ ok: false, error: "Failed to publish" }),
      {
        status: 500,
        headers: { "Content-Type": "application/json" },
      }
    );
  }
}

When a user creates or updates a workflow in the editor:

  • The component compiles the workflow into JSON.
  • It then sends this JSON to /api/publish using a POST request.
  • The request includes a channel, an event name, and the compiled workflow as the payload.
  • Your API route is responsible for receiving this data and broadcasting it (for example, using Pusher) so that robots or other clients can react to the workflow in real time.

This means that in order to use the editor effectively, you need to implement a /api/publish endpoint in your Next.js app that can handle these requests and forward them to your real‑time infrastructure.


Development

If you want to contribute:

git clone https://github.com/your-org/robogpt-nodes.git
cd robogpt-nodes
npm install
npm run build

License

MIT © 2025 RoboGPT