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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@cisl/express

v1.0.4

Published

An opinionated express depending on cog.json

Downloads

7

Readme

@cisl/express

An opinionated wrapper around the popular express and websockets/ws libraries. It assumes that you are running an application with a cog.json file.

The library assumes that you want to use cookie-parser, JSON (with 2 spaces), and the ejs as the view engine. Finally, the port is read in from the cog.json file.

Installation

npm install @cisl/express

Usage

In straight JS:

const express = require('@cisl/express');
const app = express();
app.listen();

or in TypeScript:

// or typescript
import express from '@cisl/express';
const app = express();

app.listen();

The listen method above does not accept any parameters, and will automatically use the port specified in the cog.json file that should exist in current working directory when running the above.

After creating the object, it can be used as a regular express app:

app.get('/', (req, res) => {
    res.json({'msg': 'Hello World'});
});

as well as accessing the attached WebSocket server:

app.wsServer.on('connection', (socket) => {
    console.log('a user connected');
    socket.on('message', data => {
        console.log(`Received: ${data}`);
        socket.send('pong');
    });
});

The available objects off the original (in addition to the normal express stuff) is:

  • expressListen - original express listen method, should largely not be necessary/used over listen()
  • httpServer - the underlying HttpServer instance
  • wsServer - the underlying WebSocket.Server instance

Finally, the package will automatically add a /test GET route that returns a JSON object with the following definition:

{
    "response": "AOK",
    "error": null
}

which can be used as a small healthcheck for apps running @cisl/express.

Configuration

Using this package assumes you have a cog.json file with at least the following in it:

{
    "port": number
}

Output

@cisl/express will only output a single line when you run the listen() command with the following message @cisl/express listening on port <PORT>. This will be output as a standard console.log, or if you have @cisl/logger installed, using logger.info. You can silence the output, by sending {quiet: True} to the express() method above.