High-Level SDKs

Domain-specific SDKs built on top of @nolag/js-sdk. Each SDK provides a purpose-built API for a specific use case, handling topics, presence, reconnection, and state management out of the box.

All high-level SDKs share the same architecture: a MainClass manages the connection, lobby presence, and rooms, while a RoomClass handles topic subscriptions and domain-specific state. Each SDK peer-depends on @nolag/js-sdk ^1.0.0.

Communication

Chat

@nolag/chat

Multi-room chat with presence, typing indicators, message replay, and user mapping.

Notify

@nolag/notify

Real-time notifications with channels, read/unread tracking, and badge counts.

Engagement

Stream

@nolag/stream

Live streaming engagement with comments, reaction bursts, and polls.

Feed

@nolag/feed

Activity feeds with posts, likes, comments, and fan-out delivery.

Data

Dash

@nolag/dash

Live dashboards with real-time metrics, time-series aggregation, and widgets.

Track

@nolag/track

Vehicle and asset GPS tracking with geofencing and location history.

Sync

@nolag/sync

Real-time data sync with document CRUD, version tracking, and conflict resolution.

Infrastructure

Queue

@nolag/queue

Real-time job queues with lifecycle tracking, progress updates, and worker management.

IoT

@nolag/iot

IoT device telemetry and command dispatch with acknowledgment tracking.

Collaboration

Collab

@nolag/collab

Real-time collaboration with operations, cursor tracking, and idle awareness.

Architecture

Every high-level SDK follows the same invariant pattern:

Layer	Role	Example
MainClass	Wraps `NoLag()` client, manages lobby presence, room join/leave, reconnect restoration	`NoLagChat`, `NoLagSignal`
RoomClass	Wraps `RoomContext`, subscribes to domain topics, delegates to managers	`ChatRoom`, `SignalRoom`
Managers	Handle domain-specific state (stores, trackers, resolvers)	`MessageStore`, `PeerManager`

Installation

Each SDK is published as a separate npm package:

npm install @nolag/chat @nolag/js-sdk

All SDKs peer-depend on @nolag/js-sdk ^1.0.0, which must be installed alongside.