
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
A simple WebSocket wrapper that offers some convenient methods like Socket.io does.
A simple wrapper of WebSocket-compatible objects (i.e. any object that matches the IWebSocket interface) to provide some convenient Socket.io-like methods (such as on(), off(), emit()). It is designed to be used in a NodeJS server as well as in a browser client, both of which can be written in either TypeScript or JavaScript.
A simple example:
// Common test values
const SERVER_PORT = 3001
const TEST_ENDPOINT = '/test'
const WS_URL = `ws://localhost:${SERVER_PORT}${TEST_ENDPOINT}`
// Set up the NodeJS server side
const { SimplyWS } = require('simplyws')
const expressWs = require('express-ws')
const app = require('express')()
expressWs(app)
app.ws(TEST_ENDPOINT, async (clientWs, request) => {
const simplyWS = new SimplyWS({ socket: clientWs })
simplyWS.on('echo', message => simplyWS.emit('echo-response', message))
simplyWS.on('greet', ({ name, age }) => simplyWS.send(`Hi ${name}, ${age} years old`))
})
server = app.listen(SERVER_PORT)
// Set up a NodeJS client
const { SimplyWS } = require('simplyws')
const WebSocket = require('ws')
const simplyWSClient = new SimplyWS({ socket: new WebSocket(WS_URL) })
simplyWSClient.on('echo-response', message => console.log(message)) // You should see: Hello
simplyWSClient.on('message', message => console.log(message)) // You should see: Hi Mike, 30 years old
simplyWSClient.on('open', () => {
simplyWSClient.emit('echo', 'Hello')
simplyWSClient.emit('greet', { name: 'Mike', age: 30 })
})
export const WS_EVENT = {
OPEN: 'open',
ERROR: 'error',
CLOSE: 'close',
MESSAGE: 'message'
}
export const WS_READY_STATE = {
CONNECTING: 0,
OPEN: 1,
CLOSING: 2,
CLOSED: 3
}
export declare enum WS_EVENT_RUN_MODE {
/**
* For example:
* - If a handler for 'open' is added when readyState = OPEN, then
* execute that handler immediately.
* - If a handler for 'close' is added when readyState = CLOSED, then
* execute that handler immediately.
* - If a handler for 'message' is added and the corresponding message matches a custom event,
* then run both the custom event handler and this message handler.
*/
AS_MUCH_AS_POSSIBLE = 0,
/**
* For example:
* - If a handler for 'open' is added when readyState = OPEN, then skip
* executing that handler immediately.
* - If a handler for 'close' is added when readyState = CLOSED, then skip
* executing that handler immediately.
* - If a handler for 'message' is added and the corresponding message matches a custom event,
* then run only the custom event handler and skip this message handler.
*/
AS_LESS_AS_POSSIBLE = 1
}
export interface IWebSocket {
readyState: number;
send(message: any): any;
close(): any;
}
export interface ISimplyWSOptions {
/**
* The url to the WebSocket endpoint to connect to.
*/
url?: string;
/**
* By default, true.
*/
autoConnects?: boolean;
/**
* By default, it will be a call to console.error().
*/
onError?: (...args: any[]) => void;
/**
* By default, it will be a call to console.log().
*/
onLog?: (...args: any[]) => void;
/**
* The underlying websocket connection. If this is specified, then autoConnects will be treated as
* true and this socket will be used while url / socketBuilder will be ignored.
*/
socket?: IWebSocket;
/**
* A function that returns an IWebSocket object given a url to the target endpoint.
*/
socketBuilder?: (url: string) => IWebSocket;
/**
* Applied to the core WebSocket events (open, error, close, message) only.
*/
eventRunMode?: WS_EVENT_RUN_MODE;
/**
* Automatically wrap a handler with try...catch. Any occurred error will be handled by onError.
* By default, it is true.
*/
runsHandlersSafely: boolean;
}
/**
* An event emitter that allows adding/removing handlers for different events,
* emitting a specific event, as well as running a specific handler.
*/
export declare class SimplyEventEmitter {
/**
* Add a handler for a specific event and optionally specify the maximum number
* of times that handler can be called. The handler ID will be returned.
* @param eventName
* @param handler
* @param maxCalls 0 = will be called until it is removed by the caller.
*/
addHandler(eventName: string, handler: ((...args: any[]) => any) | any, maxCalls?: number): number;
/**
* Remove from the specified event all handlers having the specified IDs and
* return the emitter itself. As a result, it is possible to chain a series of
* calls to this method.
* @param eventName
* @param handlerIds
*/
removeHandler(eventName: string, ...handlerIds: number[]): SimplyEventEmitter;
/**
* Emit an event, which results in the execution of all relevant registered handlers.
* Besides the arguments passed by the caller, each handler will also receive 1 special
* argument at last that contains the tag information about this handler.
* This method will return the emitter itself. As a result, it is possible to chain a series of
* calls to this method.
* @param eventName
* @param args
*/
emit(eventName: string, ...args: any[]): SimplyEventEmitter;
/**
* Run a specified event handler of a specific event.
* Besides the arguments passed by the caller, the handler will also receive 1 special
* argument at last that contains the tag information about this handler.
* This method will return the emitter itself. As a result, it is possible to chain a series of
* calls to this method.
* @param eventName
* @param handlerId
* @param args
*/
run(eventName: string, handlerId: number, ...args: any[]): SimplyEventEmitter;
/**
* Reset this emitter.
* This method will return the emitter itself. As a result, it is possible to chain other methods to
* the call to this method.
*/
reset(): this;
}
/**
* A simple wrapper of WebSocket-compatible objects (i.e. any object that matches the IWebSocket interface)
* to provide some convenient Socket.io-like methods (such as on(), off(), emit()).
* It is designed to be used at both client and server sides.
*/
export declare class SimplyWS {
constructor(options: ISimplyWSOptions);
readonly readyState: number | undefined;
/**
* Initialize the socket if it was created with autoConnect = false and without an underlying socket.
*/
open(): SimplyWS;
/**
* Emit an event-based message with the specified arguments.
* @param {string} eventName
* @param {...any} args
*/
emit(eventName: string, ...args: any[]): SimplyWS;
/**
* Send a raw text message.
* @param message
*/
send(message: string): void;
/**
* Register a one-time handler for the specified event and return the corresponding
* handlerId which can be used later to unregister this handler. It is a shortcut
* for on(eventName, handler, 1).
* @param eventName
* @param handler
*/
once(eventName: string, handler: ((...args: any[]) => void) | any): void;
/**
* Register a handler for the specified event and return the corresponding
* handlerId which can be used later to unregister this handler.
* For the 'message' event, the handler should have this signature:
* (message: string, matchesCustomEvent: boolean) => void. When matchesCustomEvent = true,
* it means this message can be handled by a custom event handler, i.e. this 'message' handler
* can base on matchesCustomEvent to determine if a message should be handled or not.
* @param {string} eventName
* @param {function} handler
* @param {number} maxCalls The number of times this handler can be used. After that, this handler will
* be off-ed automatically. If 0 or negative, it means this handler can be used until off() is called for it.
*/
on(eventName: string, handler: ((...args: any[]) => void) | any, maxCalls?: number): number;
/**
* Unregister the specified handlers from the specified event. If no handler is specified,
* then unregister all registered handlers.
* @param {string} eventName
* @param {...any} handlerIds
*/
off(eventName: string, ...handlerIds: number[]): SimplyWS;
close(): SimplyWS;
}
FAQs
A simple WebSocket wrapper that offers some convenient methods like Socket.io does.
We found that simplyws demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.