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

@carry0987/pipeline

v1.3.10

Published

A modular and efficient pipeline processing system for registering and managing multiple processing steps with caching and event-driven mechanisms.

Downloads

105

Readme

Pipeline-JS

NPM CI

@carry0987/pipeline is a highly modular and efficient pipeline processing system designed for managing and executing a series of processing steps. It allows users to register various types of processors, prioritize their execution order, and handle events such as processor registration, property updates, and processing completion. The system also includes a caching mechanism to avoid redundant processing, making it ideal for complex data transformation and processing workflows.

Features

  • Modular Design: Easily register and manage different types of processors.
  • Event-Driven: Utilize event emitters to handle various pipeline events.
  • Caching Mechanism: Avoid redundant processing with built-in caching.
  • Flexible Configuration: Customize and extend the pipeline according to your needs.
  • Parallel Processing: Run all registered processors in parallel with the processInParallel method.

Installation

Install the package via npm:

npm i @carry0987/pipeline -D

Usage

Here's a basic example of how to create and use a pipeline:

import { Pipeline, Processor } from '@carry0987/pipeline';

// Define custom processor types
enum CustomProcessorType {
    Init,
    ProcessA,
    ProcessB,
    Final
}

// Create custom processors by extending Processor
class InitProcessor extends Processor<string, CustomProcessorType> {
    get type(): CustomProcessorType {
        return CustomProcessorType.Init;
    }
    protected async _process(data: string): Promise<string> {
        return `Init: ${data}`;
    }
}

class ProcessA extends Processor<string, CustomProcessorType> {
    get type(): CustomProcessorType {
        return CustomProcessorType.ProcessA;
    }
    protected async _process(data: string): Promise<string> {
        return `${data} | ProcessA`;
    }
}

class ProcessB extends Processor<string, CustomProcessorType> {
    get type(): CustomProcessorType {
        return CustomProcessorType.ProcessB;
    }
    protected async _process(data: string): Promise<string> {
        return `${data} | ProcessB`;
    }
}

class FinalProcessor extends Processor<string, CustomProcessorType> {
    get type(): CustomProcessorType {
        return CustomProcessorType.Final;
    }
    protected async _process(data: string): Promise<string> {
        return `${data} | Final`;
    }
}

// Initialize the pipeline with custom processors
const pipeline = new Pipeline<string, CustomProcessorType>();

pipeline.register(new InitProcessor());
pipeline.register(new ProcessA());
pipeline.register(new ProcessB());
pipeline.register(new FinalProcessor(), 10); // You can also set the priority

async function runPipeline() {
    const result = await pipeline.process('Start');
    console.log(result); // Output should be something like: "Init: Start | ProcessA | ProcessB | Final"
}

runPipeline();

API

Pipeline

Methods

  • constructor(steps?: Processor<R, PT, Partial<ProcessorProps>>[])
    Initializes a new pipeline with optional initial steps.

  • clearCache(): void
    Clears the pipeline's cache.

  • register<P extends Partial<ProcessorProps>>(processor: Processor<R, PT, P>, priority: number = -1): Processor<R, PT, P>
    Registers a new processor in the pipeline.

  • tryRegister<P extends Partial<ProcessorProps>>(processor: Processor<R, PT, P>, priority: number): Processor<R, PT, P> | undefined
    Attempts to register a new processor, returns undefined if registration fails.

  • unregister<P extends Partial<ProcessorProps>>(processor: Processor<R, PT, P>): void
    Unregisters a processor from the pipeline.

  • process(data?: R): Promise<R | undefined>
    Runs all registered processors and returns the final output.

  • processInParallel(data?: R): Promise<Array<R | undefined>>
    Runs all registered processors in parallel and returns the final results after running all steps.

Contributing

Contributions are welcome! Please open an issue or submit a pull request with your changes.

License

This project is licensed under the MIT License. See the LICENSE file for details.