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

@zsjs/ws-controller

v0.2.4

Published

--- title: ws-controller group: controllers subGroup: general ---

Downloads

28

Readme


title: ws-controller group: controllers subGroup: general

Instruction

This controller was designed for WebSocket communication. It was sealed with some logic, such as connect timeout, reconnect, and so on.

Demos

Installing

npm install @zsjs/ws-controller;

Example

import { WsController } from "@zsjs/ws-controller";

// Create a wsController instance with options.
const wsController = new WsController({
  wsOptions: {
    address: "ws://xxx.xxx.xx.xx:8800", // connect address
    onOpened: (wsCtl: WsController) => {
      wsCtl.send("Hello world"); // when connect success will call OnOpened function.
    },
  },

  // The heartbeat check is successful when a message is sent to the server, and the 
  // server responds with a message in a timely manner. If the client does not receive 
  // a message or receives a timeout, it triggers the reconnect logic.
  heartbeatOptions: {
    // heartbeat setting.
    handleHeartbeatMsg: (msg) => {
      return msg.data.includes("---- heartbeat ----"); // Checkout if is a heartbeat message.
    },
    sendMsg: "---- heartbeat ----",
  },
});

// Or you can set address by setOPtions methods.
const wsController = new WsController({});
wsController.setOptions({ wsOptions: { address: "ws://xxx.xxx.xx.xx:8800" } });

// listen events
const message = (msg) => {};
/// Listen message
wsController?.addEventListener("message", message);

/// remove listener
wsController?.removeEventListener("message", message);

// Use close and connect to control wsController.
wsController.connect(); // start connect.
wsController.close(); // close connect.

Methods

setOptions

Set the WsController instance config after you create.

params

{ wsOptions: WsConfig, heartbeatOptions: HeartbeatConfig }

example

wsController?.setOptions({ wsOptions: { address: ws://xxx.xx.xxx.xx:xxxx }})

connect

Start websocket communication

params

{ address?: string; connectTimeout?: number;} or no params

example

wsController?.connect();

close

Close the wsController

params

no params

example

wsController?.connect();

Send

Send mesage to the server

params

msg: string

example

wsController.send('Hello world');

addEventListener && and removeEventListener

Listen the message or log change.

params

eventName: 'message' | 'log', fun: (e: any) => void

example

// Add log listener
const logReceiver = (msg: string) => {
  console.log(msg);
};
wsController?.addEventListener<string>("log", logReceiver);

// Add message listener
const messageReceiver = (msg: MessageEvent) => {
  console.log(msg);
};
wsController?.addEventListener<MessageEvent>("message", messageReceiver);

// Add message listener
const statusReceiver = (msg: SocketStatus) => {
  console.log(msg);
};
wsController?.addEventListener<SocketStatus>("message", statusReceiver);

// Remove the listener before you leave.
wsController.removeEventListener("log", logReceiver);
wsController.removeEventListener("message", messageReceiver);
wsController.removeEventListener("status", statusReceiver);

Configs

wsConfig

 interface WsConfig {
  address: string;
  connectTimeout?: number;
  reconnectIntervalTime?: number;
  retry?: number | null;
  heartBeatConfig?: HeartbeatConfig
  onOpened?: Function
}

HeartbeatConfig

 interface HeartbeatConfig {
  handleHeartbeatMsg?: (msg: any) => boolean,
  timeout?: number,
  intervalTime?: number,
  sendMsg?: string
}