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 🙏

© 2024 – Pkg Stats / Ryan Hefner

hibot

v0.1.19

Published

Just a bot.

Downloads

34

Readme

hibot

Just a bot.

Installation

Simple install as a dependency using npm:

npm install -g hibot

Usage

import { createServer } from "hibot";

type TaskResponse<T = any> = {
  id: TaskId;
  response: T;
  cost: number;
  start: number;
  ended: boolean;
};

let server = createServer({
  port: 30000,
  onConnection(nodeId) {
    console.log(`node[${nodeId}] is online.`);
    server.boot(task);
  },
  onHeartbeat(clientId, stats: ClientStats) {},
  onClose(nodeId) {
    console.log(`node[${nodeId}] is offline.`);
  },
  onResponse(nodeId, taskResponse: TaskReponse) {},
});

You can also use a custom ws server.

import { createServer } from "hibot";
import { WebSocketServer } from "ws";

let server = createServer({
  onConnection(nodeId) {
    console.log(`node[${nodeId}] is online.`);
    server.boot(task);
  },
  onHeartbeat(clientId, tasks) {},
  onClose(nodeId) {
    console.log(`node[${nodeId}] is offline.`);
  },
  onResponse(nodeId, taskResponse: TaskReponse) {},
});

const wss = new WebSocketServer({ port: 30000 });

wss.on("connection", (ws) => {
  server.createClient(ws);
});

CLI

Server CLI

hibot server start | stop | status

Options:
  -p, --port            server port, default 30000
  -t, --token           token
  -ap,--api_server_port api server port,default 30001
  -d, --daemon          run in deamon

Client CLI

hibot client start | stop | status

Options:
  -id,--id             client id
  -t, --token          token
  -pf,--platform       vendor, default 'pptr'
  -d, --daemon         run in deamon

API

/{api}?token={token}

| | method | api | body | response | | --------------- | ------ | ----------------------------------------------------- | ---- | ------------------------------ | | boot task | PUT | /tasks | Task | | | stop task | GET | /task/{task_id}/stop | | | | task screenshot | GET | /task/{task_id}/screenshot?type={jpeg/png/webp/mjpeg} | | | | clients | GET | /clients | | Response<Array<ClientStats>> | | client | GET | /client/{client_id} | | Response<ClientStats> |

type Response<T> = { code: number; data: T };

enum TRIGGER_TYPE {
  TIMER = "timer",
  LOOP = "loop",
}

type PPTROptions = {
  windowSize?: string;
  proxyServer?: string;
  cookies?: string;
  userAgent?: string;
};
type Task = {
  id: string;
  clientId: string;
  triggerType?: TRIGGER_TYPE;
  // cron expression for timer
  // time expression(e.g. 1h2m3s) for timer
  triggerVal?: string;
  remoteApi?: string;
  script: string;
  // The task remains after the bot is completed.
  keepalive?: boolean;
  options?: PPTROptions | Record<string, any>;
};

enum TASK_STATE {
  CLOSED = 1,
  RUNNING = 2,
}

type ClientStats = {
  id: string;
  tasks: Array<{ id: string; state: TASK_STATE }>;
  usage: {
    cpu: number; //percentage (from 0 to 100*vcore)
    memory: number; //bytes
    elapsed: number; //ms since the start of the process
    timestamp: number; //ms since epoch
  };
};

License

MIT
Copyright (c) 2020-present, Reruin