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 🙏

© 2026 – Pkg Stats / Ryan Hefner

lynx-chat

v0.0.1

Published

Chat module for the lynx framework

Readme

Lynx Chat Module

This module adds chat functionality to the lynx framework.

The frontend is implemented as a React application, that can be easily integrated as an iframe. The backend is currently implemented as REST APIs, and the React application perform a polling-like method to update the message list.

Installation and usage

The Chat Module depends on the Lynx Admin UI module to provide a basic automatic administration area.

For installation:

npm install lynx-datagrid lynx-admin-ui lynx-chat

A typical configuration could be:

import AdminUIModule from 'lynx-admin-ui';
import DatagridModule from 'lynx-datagrid';
import { App, ConfigBuilder } from 'lynx-framework';
import ChatModule from '..';

const port = Number(process.env.PORT) || 3000;

let myConfig = new ConfigBuilder(__dirname, false).build();

const app = new App(myConfig, [
    new DatagridModule(),
    new AdminUIModule(),
    new ChatModule(),
]);

app.startServer(port);

Rooms, users and message types

The module supports multiple rooms (or channel). Each room can contain multiple users.

Users can be associated with a standard lynx UserEntity, or they can be guest-user.

To create a new user, it is possible to execute the following code:

//creation of a chat guest user, named 'Boris'
let userA = await ChatUserEntity.createUser('Boris');

//creation of a chat user connected to a lynx standard user
let userB = await ChatUserEntity.createUser(lynxStandardUser);

To create a new room, it is possible to execute the following code:

let room = await ChatRoomEntity.createRoom('Jellyfish', [userA, userB, userC]);

in this example, a new room named 'Jellyfish' is created, formed by three users.

The module supports text messages and file messages. For the latter, each uploaded file will be a Media object, stored inside the /chat/uploads virtual directory.

Integrate the frontend

The frontend is available at the following path:

/chat/app/index.html?room={{roomId}}&id={{chatUserId}}

where roomId specify the id of the room to use; the chatUserId specify the current Chat User Id that sends the message.

IMPORTANT: the frontend should always used inside an iframe or similar and the url should be as masked as possible to the end user. Moreover, to provide security for user access, a middleware should be provided.

Security and validations

The API endpoints are in the /chat/api/ path. You should provide your own middleware to provide security (if needed) on the access of this endpoints.