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

trello-notification-stream

v0.1.1

Published

A node.js stream that emits trello notifications for a single user

Downloads

7

Readme

trello-notifications-stream

A node.js stream that emits trello notifications for a single user, in the format output by the Trello API. This stream does not end, it continues to emit notifications as they occur.

Installation

Install via npm:

$ npm install trello-notifications-stream

Example

notifications = require('trello-notifications-stream')
stdout = require('stdout')

options = {
  key: 'your_trello_api_key',
  token: 'your_trello_api_token',
  username: 'your_trello_username',
  interval: (1000 * 60 * 15)
}

notifications(options).pipe(stdout())

The notifications stream is an object stream, so here I'm piping it to the stream provided by the stdout package which handles outputting objects to stdout.

As the notifications stream does not end, it keeps checking for notifications by polling the trello API regularly, the interval time suppied (in milliseconds) is the minimum time between polls. If backpressure is exerted on this stream, or the stream is paused for any reason, then this timer is paused. So, it's possible that the actual time between polls is longer than the supplied interval, but it should never be shorter.

Only unique notifications are returned. If it polls the notifications API again and only sees the same notification ids, it wont return anything new. The filtering out of non-unique notifications is done by storing a list of notification ids. By default this is done in memory, so if you create a new stream it will emit all the notification again.

If you would like to store the keys more permanently so that you can re-start the stream and not receive notifications again, then pass in a key store object which supports has(key) and add(key) methods.

notifications = require('trello-notifications-stream')
stdout = require('stdout')

myStore = {
  store: {}

  add: (key) ->
    @store[key] = true

  has: (key) ->
    @store[key] !== undefined
}

options = {
  key: 'your_trello_api_key',
  token: 'your_trello_api_token',
  username: 'your_trello_username',
  keyStore: myStore
}

notifications(options).pipe(stdout())