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

@torv-pipe/node-sdk

v1.0.0

Published

SDK for building ETL stages in Node.js/TypeScript

Readme

@pipe/node-sdk

SDK for building ETL stages in Node.js/TypeScript, with built-in codegen CLI.

Installation

npm install @pipe/node-sdk

Usage

Writing Stages

import { StageRunner, StageContext, successResult } from '@pipe/node-sdk';

const myStage: StageRunner = async (context: StageContext) => {
  const { logger, params, inputs } = context;
  
  // Your stage logic here
  return successResult({ output: 'result' });
};

export default myStage;

Generating Types

The SDK includes a CLI tool for generating TypeScript types from proto contracts:

# Generate types once
npx pipe-codegen --proto-dir=../torv-proto --stage-dir=./stages/my_stage

# Watch mode (regenerates on changes)
npx pipe-codegen --proto-dir=../torv-proto --stage-dir=./stages/my_stage --watch

The CLI will:

  1. Look for a proto service matching your stage name (e.g., MyStage service for my_stage stage)
  2. Extract input/output contracts from the service
  3. Generate TypeScript types in .etl/generated/

Using Generated Types

import { Inputs, Outputs } from './.etl/generated';
import { StageRunner, successResult } from '@pipe/node-sdk';

const myStage: StageRunner = async (context) => {
  // Full type safety!
  const input: Inputs['primary'] = context.inputs.primary;
  const output: Outputs['result'] = transform(input);
  
  return successResult({ result: output });
};

CLI Options

pipe-codegen [generate] --proto-dir=<dir> --stage-dir=<dir> [--watch]

Options:
  --proto-dir=<dir>    Directory containing .proto files
  --stage-dir=<dir>    Stage directory (where .etl/generated will be created)
  --watch, -w          Watch for changes and regenerate

Proto Contract Format

Define your stage contract using a proto service:

service MyStage {
    rpc Execute(MyStageInput) returns (MyStageOutput);
}

message MyStageInput {
    Address primary = 1;
}

message MyStageOutput {
    EnrichedAddress result = 1;
}

The service name must match your stage name in PascalCase (e.g., my_stageMyStage).