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

server-events-nodejs

v0.2.1

Published

A library for setting up server-sent events in Node.js

Downloads

18

Readme

server-events-nodejs

A library for setting up server-sent events in Node.js. This library was inspired by work done by Dino Paskvan on express-sse

Install

npm

npm install server-events-nodejs --save

yarn

yarn add server-events-nodejs

Usage


const { Source, EventStream } = require('server-events-nodejs');

const express = require('express');
const cuid = require('cuid');
const port = "8080";

const source = new Source(cuid);
const app = express();

app.listen(port, () => {
  console.log('Server ready!');
});

app.use(
  EventStream.init(source, { 
    no_ids: false, // if you need id: key/value (from the cuid lib) as part of the text-stream response - set to 'true'
    pad_for_ie: false, // if the HTTP request is from an IE 8/9 browser - set to 'true'
    prefered_event_name: 'update', // if you need event: key/value (here set to 'update')  as part of the text-stream resposne - set here to whatever you like
    prefer_event_name: true // enforce the prefered event name to be used in the text-stream response
  })
);

app.get('/notifications', function(req){
    console.log('headers: ', req.headers);

    // send comment: '!this is a comment!'
    // send with event name: 'update'
    // send with retry: 4500 (4.5 seconds)
    source.send({
            ids: [ '123', '456' ],
            timestamp: Date.now()
      }, 
      '!this is a comment!', // comment
      'update', // event
      4500 // retry
    );
    
});

Then, you need to setup the front-end accordingly


const evtSource = new EventSource('http://localhost:8080/notifications');

evtSource.addEventListener('open', function(e) {
  console.log("connection is open!");
}, false);

evtSource.addEventListener('error', function(e) {
  console.error(e);
  evtSource.close();
})

evtSource.addEventListener('update', function(e) {
  console.log("message: ", JSON.parse(e.data));
}, false);

/* - logs to console -

  connection is open!

  message: {
    "ids": [
      "123",
      "456"
    ],
    "timestamp": 1608970168797
  }
  
*/

License

MIT