1.1.0 • Public • Published


Build Status

tab-sockets is a library designed to help you make different tabs of the same website communicate together effectively. tab-sockets uses localStorage and listeners to achieve this communication, and as such, only works in browsers which support localStorage.


You can install the package by running

npm install tab-sockets


tab-sockets can be used directly in the browser as a <script> tag or included into a browserified bundle. tab-sockets will not work outside the browser, as Node has no localStorage.

When being included in the browser with a script tag, the tag's src attribute should point to dist/tab-sockets.min.js, which is the minified build of the library for browsers. When using the library in this manner, the main function of the library will be contained in the global io variable.

For the documentation below, I assume that if you are importing the library for later bundling, you are importing it to the variable io.


The documentation below is similar to the documentation of

Socket Creator


Returns a socket which is linked to this namespace. Namespace is immutable for this socket. If no namespace is given, the socket listens to the default namespace. Only sockets specifically listening to a namespace will receive events from that namespace. All events emitted by this socket will go only to the declared namespace.

A socket automatically joins the room equalling it's id when created.



Joins a specific room. Rooms are used to segregate messages and a message sent to a specific room will only be received by sockets that have joined it.


Leaves a specific room. This will prevent the socket from receiving messages sent to that room in the future.

.on(type, fn)

Registers a listener for a type of event. The callback function will be executed when an event is emitted of this type, giving the data of the event as the first argument to the callback and the id of the emitting socket as the second.


Adds a room for the next emit to be sent to. These functions return the same object, so they can be chained for multiple rooms to be targeted. If no rooms are declared for an emit, the emit will go to all rooms. The list of rooms targeted by an emit gets reset after the emit is executed.

.emit(eventType, [data])

Emits a message of the specified type with the specified data attached. All sockets, including the sender, will receive this emission as long as they fulfill the rules of namespaces and rooms.


This is a flag that you can set on the socket before you emit to prevent the emitting socket from also receiving the message. This flag returns the same socket object. Use the flag like this socket.broadcast.emit('test-event-type', 'test');

Example Usage

const io = require('tab-sockets');
//Get socket with the default namespace
var socket = io();
//Joining the test room
socket.join('test room');
socket.on('ping', function(data){
.to('test room')
.emit('ping', 'other sockets get this message');
.to('test room')
.emit('ping', 'the emitting socket will also get this message');


Make sure your code is in the xo style. One of the steps in the testing script is to check all files for style violations.

Run npm test to generate a new minified file, which tests will be run against.

Run npm run build to only build a new minified file.



npm i tab-sockets

DownloadsWeekly Downloads






Last publish


  • cakenggt