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

websocket-with-heartbeat

v0.0.21

Published

A TypeScript WebSocket client wrapper with built-in heartbeat mechanism and auto-reconnection support.

Downloads

300

Readme

WebSocketWithHeartbeat

A TypeScript WebSocket client wrapper with built-in heartbeat mechanism and auto-reconnection support.

Features

  • Automatic heartbeat detection (ping/pong)
  • Auto-reconnection on connection loss
  • Page visibility-based connection management
  • Strict message type checking
  • Support for JSON/binary message format
  • Full TypeScript support

Installation

npm install websocket-with-heartbeat

Usage

Basic Example

import WebSocketWithHeartbeat, { WebSocketMessage } from 'websocket-with-heartbeat'

// Initialize
const ws = new WebSocketWithHeartbeat('wss://example.com', {
  debug: true
})

// Manual connection
ws.connect()

// Handle incoming messages
ws.onmessage = (event) => {
  const message: WebSocketMessage = event.data
  switch (message.type) {
    case 'chat':
      console.log('Chat message:', message.content)
      break
    case 'notification':
      console.log('Notification:', message.text)
      break
  }
}

// Send message
ws.send({
  type: 'chat',
  content: 'Hello!',
  timestamp: Date.now()
})

Message Type Definition

All messages must follow the WebSocketMessage interface:

interface WebSocketMessage {
  type: string;
  [key: string]: any;
}

Note: The type field is required for all messages. Messages not following this format will be rejected.

Reserved Message Types

  • ping: Used internally for heartbeat requests
  • pong: Used internally for heartbeat responses

Configuration Options

interface WebSocketOptions {
  heartbeatInterval?: number;  // Heartbeat interval (default: 30000ms)
  reconnectDelay?: number;     // Delay before reconnection attempts (default: 5000ms)
  timeout?: number;            // Heartbeat timeout (default: 5000ms)
  debug?: boolean;             // Enable debug logs (default: false)
  messageType?: 'json' | 'binary';  // Message format (default: 'json')
}

Event Handlers

ws.onopen = (event: Event) => {
  console.log('Connected')
}

ws.onmessage = (event: { data: WebSocketMessage }) => {
  // Note: event is not a native MessageEvent
  console.log('Message received:', event.data)
}

ws.onclose = (event: CloseEvent) => {
  console.log('Disconnected')
}

ws.onerror = (event: Event) => {
  console.log('Error occurred')
}

Connection Management

// Manual close
ws.close()

// Connection automatically manages based on page visibility:
// - Connects when page becomes visible
// - Disconnects when page becomes hidden

Debug Mode

When debug: true is set, the library will log detailed connection and message information to the console.

License

MIT