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 🙏

© 2026 – Pkg Stats / Ryan Hefner

iii-sdk

v0.2.0

Published

III SDK for Node.js

Readme

III SDK for Node.js

Installation

npm install iii-sdk

Usage

import { III } from 'iii-sdk'

/**
 * Make sure the III Core Instance is up and Running on the given URL.
 */
const iii = new III(process.env.III_BRIDGE_URL ?? 'ws://localhost:49134')

iii.registerFunction({ id: 'myFunction' }, (req) => {
  return { status_code: 200, body: { message: 'Hello, world!' } }
})

iii.registerTrigger({
  type: 'http',
  function_id: 'myFunction',
  config: { api_path: 'myApiPath', http_method: 'POST' },
})

Registering Functions

III Allows you to register functions that can be invoked by other services.

iii.registerFunction({ id: 'myFunction' }, (req) => {
  // ... do something
  return { status_code: 200, body: { message: 'Hello, world!' } }
})

Registering Triggers

III Allows you to register triggers that can be invoked by other services.

iii.registerTrigger({
  type: 'http',
  function_id: 'myFunction',
  config: { api_path: 'myApiPath', http_method: 'POST' },
})

Registering Trigger Types

Triggers are mostly created by III Core Modules, but you can also create your own triggers

iii.registerTrigger_type(
  {
    /**
     * This is the id of the trigger type, it's unique.
     * Then, you can register a trigger by calling the registerTrigger method.
     */
    id: 'myTrigger_type',
    description: 'My trigger type',
  },
  {
    /**
     * Trigger config has: id, function_id, and config.
     * Your logic should know what to do with the config.
     */
    registerTrigger: async (config) => {
      // ... do something
    },
    unregisterTrigger: async (config) => {
      // ... do something
    },
  },
)

Invoking Functions

III Allows you to invoke functions, they can be functions from the Core Modules or functions registered by workers.

const result = await iii.call('myFunction', { param1: 'value1' })
console.log(result)

Invoking Functions Async

III Allows you to invoke functions asynchronously, they can be functions from the Core Modules or functions registered by workers.

iii.callVoid('myFunction', { param1: 'value1' })

This means the Engine won't hold the execution of the function, it will return immediately. Which means the function will be executed in the background.