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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@anthriq/registry-stack

v1.0.0

Published

Node.js SDK for Registry Stack - Operator Registry, Pipeline Registry, and Executor

Readme

Registry Stack Node.js SDK

npm version License: MIT Node.js Version

A comprehensive Node.js SDK for the Registry Stack, providing TypeScript/JavaScript interfaces for Operator Registry, Pipeline Registry, and Executor operations.

Installation

npm install @anthriq/registry-stack

Quick Start

Executor Operations

import { Executor } from '@anthriq/registry-stack';

// Initialize the executor
const executor = new Executor({
  basePath: '/tmp/executor',
  bridgeLibPath: '/path/to/libexecutor_bridge.dylib',
  debug: true
});

await executor.initialize();

// Create a pipeline
const result = await executor.create({
  config: {
    jsonFile: '/path/to/pipeline.json',
    background: true
  },
  deviceId: 'my-device-001',
  enableLogging: true,
  onUnifiedLog: (entry) => {
    console.log('Log:', entry.message, 'from', entry.source);
  }
});

if (result.status === 'success') {
  console.log('Pipeline created:', result.data.pipeline_id);
  
  // Start the pipeline
  await executor.start(result.data.run_id);
  
  // Stop the pipeline
  await executor.stop(result.data.run_id);
  
  // Destroy the pipeline
  await executor.destroy(result.data.run_id);
}

Unified Logging

The SDK provides structured logging with rich context:

interface UnifiedLogEntry {
  // Core identification
  node_id: string;
  pipeline_id: string;
  run_id: string;
  device_id: string;
  
  // Log metadata
  level: number;        // 0=DEBUG, 1=INFO, 2=WARNING, 3=ERROR, 4=CRITICAL
  source: number;       // 0=NODE, 1=EXECUTOR, 2=PIPELINE, 3=SDK, 4=SYSTEM
  message: string;
  
  // Timing information
  timestamp: number;
  elapsed_ms: number;
  
  // Context information
  function_name: string;
  file_name: string;
  line_number: number;
  
  // Additional data
  data: any;
  metadata: Record<string, any>;
  
  // SDK specific fields
  sdk_component?: string;
  sdk_operation?: string;
}

Log Sources

  • NODE (0): C++ pipeline nodes
  • EXECUTOR (1): Executor core operations
  • PIPELINE (2): Pipeline management
  • SDK (3): Node.js SDK operations
  • SYSTEM (4): System components

Log Levels

  • DEBUG (0): Detailed debugging information
  • INFO (1): General information
  • WARNING (2): Warning messages
  • ERROR (3): Error conditions
  • CRITICAL (4): Critical failures

API Reference

Executor

new Executor(options)

Create a new Executor instance.

Options:

  • basePath: string - Base directory for executor operations
  • bridgeLibPath: string - Path to the native bridge library
  • debug?: boolean - Enable debug logging

executor.initialize()

Initialize the executor and load the native bridge.

executor.create(options)

Create a new pipeline.

Options:

  • config: { jsonFile?: string, jsonData?: string, background?: boolean }
  • deviceId?: string
  • enableLogging?: boolean
  • onUnifiedLog?: (entry: UnifiedLogEntry) => void

Returns: Promise<PipelineCreateResponse>

executor.start(runId)

Start a pipeline execution.

executor.stop(runId)

Stop a pipeline execution.

executor.destroy(runId)

Destroy a pipeline and clean up resources.

Requirements

  • Node.js >= 16.0.0
  • Native bridge library (libexecutor_bridge.dylib/libexecutor_bridge.so)