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

evno

v0.6.0

Published

JavaScript library to participate in a value-adding network using [Event Notifications](https://www.eventnotifications.net/) and Solid pods.

Downloads

8

Readme

Event Notifications Typescript library

JavaScript library to participate in a value-adding network using Event Notifications and Solid pods.

Install

yarn install
yarn build 
yarn link

Usage in NodeJS

Receiving event notifications from an LDN inbox

import { Receiver } from "evno"
const options = {
  name: "", email: "", password: "", idp: ""
}
const receiver = await Receiver.build(options);
receiver.start("https://localhost:3000/inbox","notification_id") // Use the notifcation strategy
receiver.on('notification', async (n) => {
  // print notification
  console.log(n)

  // stop the watcher
  receiver.stop()
})

Listening to errors

import { Receiver } from "evno"
const options = {
  name: "", email: "", password: "", idp: ""
}
const receiver = await Receiver.build(options);
receiver.start("https://localhost:3000/inbox","notification_id") // Use the notifcation strategy
receiver.on('error.parsing', async (e) => {
  console.log(e)
})
receiver.on('error.fetch', async (e) => {
  console.log(e)
})
receiver.on('error', async (e) => {
  console.log(e)
})

| Event | Description | | ----- | ----------- | | error.fetch| Fetching the notification resource failed | | error.parsing| The notification was fetched, but failed to parse. | | error| An error occurred with processing the notification. |

Initalizing an LDN inbox in a Solid pod

import { Receiver } from "evno"
const options = {
  name: "", email: "", password: "", idp: ""
}
const receiver = await Receiver.build(options);
const inbox = await receiver.init("https://localhost:3000/", "inbox/");
console.log(inbox) // "https://localhost:3000/inbox/"

Grant an agent quick append access to an LDN inbox in a Solid pod

import { Receiver } from "evno"
const options = {
  name: "", email: "", password: "", idp: ""
}
const receiver = await Receiver.build(options);
await receiver.grantAccess("https://localhost:3000/inbox/", "https://example.org/webid#me");

Sending an event notification

import { Sender } from "evno"
const options = {
  name: "", email: "", password: "", idp: ""
}

const actor = {
  id: "http://example.org/me"
}

const sender = Sender.build(actor, options);
const response = sender.send() // Returns a Fetch API Response object

if (response.ok) {
  console.log('The notification was sent successfully')
}

one-way pattern

import { Sender } from "evno"
const options = {
  name: "", email: "", password: "", idp: ""
}

const actor = {
  id: "http://example.org/me"
}

const sender = Sender.build(actor, options);

// Send an Announce
await sender.announce("https://acme.org/artifacts/alice/five_steps_to_success.html") 

// Send a Create 
await sender.create("https://acme.org/artifacts/alice/five_steps_to_success.html")

// Send an Update
await sender.update("https://acme.org/artifacts/alice/five_steps_to_success.html")

// Send a Remove
await sender.remove("https://acme.org/artifacts/alice/five_steps_to_success.html")

The previous examples assume autodiscovery of the inbox. You can also supply the inbox explicitely as follows:

await sender.announce("https://acme.org/artifacts/alice/five_steps_to_success.html", "https://example.org/inbox/") 

// If the target inbox uses different credentials, you can override the default ones as well
await sender.announce("https://acme.org/artifacts/alice/five_steps_to_success.html", "https://example.org/inbox/", {
  name: "", email: "", password: "", idp: ""
}) 

Request-response pattern

Sending the request:

import { Sender } from "evno"
const options = {
  name: "", email: "", password: "", idp: ""
}

const actor = {
  id: "http://example.org/agentA"
}

const sender = await Sender.build(actor, options);

// Announce
await sender.offer("https://acme.org/artifacts/alice/five_steps_to_success.html", "https://localhost:3000/inbox") 

Sending the response:

import { Sender, Receiver } from "evno"

// Authentication options for target inbox
const optionsSender = {
  name: "", email: "", password: "", idp: ""
}

// Authentication options for own inbox
const optionsReceiver = {
  name: "", email: "", password: "", idp: ""
}

const actor = {
  id: "http://example.org/agentB"
}

const sender = await Sender.build(actor, optionsSender);
const receiver = await Receiver.build(optionsReceiver);
receiver.start("https://localhost:3000/inbox","notification_id") // Use the notifcation strategy
receiver.on('notification', async (n) => {
  // Do something with notification

  await sender.accept(n)
  // OR
  await sender.reject(n)
})

Usage in command-line

  _____                 _   _   _       _   _  __ _           _   _                 
 | ____|_   _____ _ __ | |_| \ | | ___ | |_(_)/ _(_) ___ __ _| |_(_) ___  _ __  ___ 
 |  _| \ \ / / _ \ '_ \| __|  \| |/ _ \| __| | |_| |/ __/ _` | __| |/ _ \| '_ \/ __|
 | |___ \ V /  __/ | | | |_| |\  | (_) | |_| |  _| | (_| (_| | |_| | (_) | | | \__ \
 |_____| \_/ \___|_| |_|\__|_| \_|\___/ \__|_|_| |_|\___\__,_|\__|_|\___/|_| |_|___/
                                                                                    
Usage: evno [options] [command]

A CLI for using Linked Data Notification in Solid Pods

Options:
  -V, --version                        output the version number
  -n, --name <username>                Username
  -e, --email <email>                  Email
  -p, --password <password>            Password
  -i, --idp <idp>                      Identity provider (default: "http://localhost:3001/")
  -t, --tokenLocation <tokenLocation>  Client token storage location (default: "./")
  -v, --verbose                        Output verbose logging (default: false)
  -h, --help                           display help for command

Commands:
  receive [options] <inboxUrl> [path]  Watch an inbox for new notifications
  init <baseUrl> [inboxPath]           Initialize an inbox
  grant <inboxUrl> <agentUri>          Grant an agent access to inbox
  login                                Generate a login token at the specified location
  send [options] <inboxUrl> <path>     Send a notification to a inbox
  help [command]                       display help for command