Registry / messaging / websocket-conference-server

websocket-conference-server

JSON →
library0.8.2jsnpmunverified

An out-of-the-box HTTP and WebSocket server for multi-client conference sessions, built on the `websocket` module (WebSocket-Node). Current stable version is 0.8.2, with no active release cadence (last update likely years ago). Its key differentiator is zero-config setup for rapid prototyping on Node.js >=0.12.2, serving static files and hosting a WebSocket conference with custom protocols and utilities. It is a thin abstraction layer over `websocket`, not actively maintained, and has limited documentation.

npm install websocket-conference-server
INSTALL
IMPORT
SIG · WEBSOCKET-CONFEREN
W
websocket-conference-server
messagingjavascriptv0.8.2
harness data pending
Install & Compatibility
Where this runs

No compatibility data collected yet for this library.

Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

start
var server = require('websocket-conference-server').start();
const { start } = require('websocket-conference-server'); // Works but not idiomatic for this module
CommonJS only; no ESM export. `.start()` is a method on the exported object.
default export
var wscs = require('websocket-conference-server'); wscs.start(config, utilities);
import wscs from 'websocket-conference-server'; // ESM not supported
The module exports an object with a `start` method. No default export.
config object
var config = { verbosity: 1, protocol: 'my-custom-protocol', port: 8001, logs_path: 'Logs/', IP_lookup_path: 'IPs/', logs_suffix: '-alpha.log', http_paths: { 'ico': '../Assets', 'jpg': '../Assets', 'png': '../Assets', 'html': '..', 'css': '..', 'js': '..' } };
var config = { verbose: true }; // Wrong property name
Config properties must match exactly: verbosity (number), protocol (string), port (number), logs_path (string), IP_lookup_path (string), logs_suffix (string), http_paths (object with extension->path mappings).
custom_utilities
var custom_utilities = require('./my_custom_utilities'); server.start(config, custom_utilities);
server.start(config, { augment: (u) => u }); // Should be a module that augments utilities object
The second argument is a module whose exported `augment` function receives and returns the utilities object.

Starts default server on port 8000 with echo protocol and console logging.

var server = require('websocket-conference-server').start(); console.log('Server listening on port 8000');
Debug
Known issues
breakingRequires Node.js >=0.12.2, may not work on modern Node versions due to deprecated APIs.
fix
Use an older Node version or run in a legacy environment.
affects: >=0.8.2
deprecatedModule is in maintenance mode; no active development or bug fixes.
fix
Consider alternatives like ws or socket.io for new projects.
affects: >=0.8.2
gotchaThe `start()` method blocks the event loop? Check source; may not return a server object.
fix
Review source code to understand behavior; possible to call start() without callback.
affects: >=0.8.2
gotchaDefault protocol is 'echo-protocol', not custom; must specify protocol in config.
fix
Set config.protocol to your protocol name.
affects: >=0.8.2
Errors
Common errors & fixes
Error: Cannot find module 'websocket'
Dependency 'websocket' not installed automatically in some npm versions.
fix
Run: npm install websocket
TypeError: server.start is not a function
Importing module incorrectly; expecting `start` as a standalone export.
fix
Use: var server = require('websocket-conference-server'); server.start();
ReferenceError: my-custom-protocol is not defined
Protocol name must be a string, not a variable without quotes.
fix
Set config.protocol = 'my-custom-protocol';
Upgrade
Version history
0.8.2latest on npm
Audit
Dependencies
websocketrequiredWebSocket-Node module is the core WebSocket implementation
Agent activity
24 hits · last 30 days
node
20
OpenAI (training)
1
Resources
websocket-conference-server — npm install websocket-conference-server · libregistry