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

@tshio/notifications-client

v0.0.1

Published

RAD Notifications Client

Downloads

4

Readme

RAD Notifications Client

npm version

Non-blocking RAD Notifications client for Node.js.

This is a 100% JavaScript library, with TypeScript definition, with the Promise API.

This module makes it simple to implement a Node.js application that uses RAD Notifications.

Table of Contents

Installing

$ npm install @tshio/notifications-client

or

$ yarn add @tshio/notifications-client

Loading and configuration module

// CommonJS
const { PdfClient } = require('@tshio/notifications-client');

// ES Module
import { PdfClient } from '@tshio/notifications-client';


const options = {
  host: "localhost",
  port: "50080",
}

const notificationsClient = new NotificationsClient(options);

Getting started

Send notification

const message = {
   channels: ["default"],
   message: "Test message",
}
const { notificationsIds } = async notificationsClient.notifications.send(message);

Get notifications

const notifications = async notificationsClient.notifications.get();

API

notificationsClient.notifications.send({ channels, message }) => Promise<{ notificationsIds }>

Send notification

Returns an object with an array of crated notifications ids.

{
  notificationsIds: string[];
}

or throw HttpError

Parameters

| Name | Type | Description | Default | |--------------|------------|---------------------------------------|-----| | channels | string[] | Send messages to channels. | | | message | string | Notification message | |

Back to API

notificationsClient.notifications.get( queryFilter? ) => Promise

Get notifications list (if no query parameters it returns first 25 notifications ordered by created date)

Returns an object

{
  notifications: Notification[];
  total: number;
  page: number;
  limit: number;
}

interface Notification {
  id: string;
  channel: string;
  message: string;
  createdAt: Date;
}

or throw HttpError

Parameters

| Name | Type | Description | Default | |--------------|------------|---------------------------------------|-----| | queryFilter | object | optionalQuery filter | | | queryFilter.page | number | optionalPage number | 1 | | queryFilter.limit | number | optionalResponse limit | 25 | | queryFilter.filter | number | optionalFilter object | | | queryFilter.query | number | optionalQuery object | |

Filters can be used search for a single condition or they can be wrapped in logical operands AND and OR. Filtering can be a simple conditional evaluation of a single field.

export type GetNotificationsColumns = "id" | "channel" | "message" | "createdAt";

export type GetNotificationsFilterOperators = "eq" | "neq" | "lt" | "gt" | "include" ;

export interface GetNotificationsRequest {
  page?: number;
  limit?: number;
  filter?: {
    [column in GetNotificationsColumns]?: {
      [operator in GetNotificationsFilterOperators]?: string;
    };
  };
  order?: {
    by: "resource" | "attribute";
    type: "asc" | "desc";
  };
}
  • filter[column][operator] = value

    | Name | Type | Description | |-----------------------|------------|----------------------------------------------------------| | column | string | Column name | | operator | string | Operator name | | value | string or number or boolean (depending on the column type) | |

    Examples

    Single parameter filter

    filter: {
      message: {
        include: "test"
      }
    }

    Two parameter filter

    filter: {
      message: {
        include: "test"
      },
      channel: {
        eq: "default",
      },
    }
  • order

    | Name | Type | Description | Default | |-----------------------|------------|---------------------------------------------------------------------------------|---------| | by | string | optional column name for order sorting, allowed values: "id", "channel", "message", "createdAt" | id | | type | asc or desc| optional Ascending or descending order | asc |

    Examples

    order: {
      by: "id",
      type: "desc"
    }

Back to API

License

license

This project is licensed under the terms of the MIT license.

About us:

The Software House