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

mono-push

v0.7.2

Published

Mono Push module

Downloads

9

Readme

Push module for Mono

npm version Travis Coverage license

Installation

npm install --save mono-push

Then, in your configuration file of your Mono application (example: conf/application.js):

module.exports = {
  mono: {
    modules: [
      'mono-mongodb',
      'mono-push'
    ]
  }
}

mono-push requires mono-mongodb, so it must be installed and declared before mono-push because modules are loaded synchronously

Configuration

mono-push will use the push property of your configuration:

  • io: Activate push event via socket.io
    • Type: boolean
    • Default: false
    • Requires: mono-io
  • collectionName: Collection name in MongoDB
    • Type: string
    • Default: 'mono-pushes'

Example of activating socket.io and writing events in pushes collection (conf/application.js):

module.exports = {
  mono: {
    modules: [
      'mono-mongodb', // Required by mono-push
      'mono-io', // Required by mono-push when io is true
      'mono-push'
    ],
    push: {
      io: true,
      collectionName: 'pushes'
    }
  }
}

Usage

In your files, you can access the push and pushAll methods like this:

Push an event to authenticated user(s) matching a query

push(event: string, query: object = {}, payload: object = {})

Push an event to all connected sockets

pushAll(event: string, payload: object = {})

Example

const { push, pushAll } = require('mono-push')

await push('notification', { userId: '...' }, { type: 'email' })
// userId will be matched against authenticated users

await pushAll('message', { message: 'Welcome!' })
// Send it to all connected devices

With conf io: true, mono-push will emit an event to every socket connected that matches the query.

On client-side, the user must connect with the socket.io-client:

import io from 'socket.io-client'

const socket = io('http://localhost:8000/push')

const token = '...' // JWT generate by await jwt.generateJWT(session), see Mono

socket.on('connect', () => {
  socket
    .emit('authenticate', { token })
    .on('authenticated', function () {
      console.log('Authenticated')
    })
    .on('unauthorized', function (msg) {
      console.log('Unauthorized')
    })

  // Listen on push events
  socket.on('my-event', (event) {
    // event is { message: 'Welcome!' }
  })
})