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

@pipex/core

v1.1.0

Published

process data like a pipeline

Readme

@pipex/core

tag license npm version Build Status Coverage Status

What is @pipex/core?

process data like a pipeline

Design

Usage

const value = {
    name: '@pipex/core',
    loading: false
};
const customStart = {
    getName(value) {
	return `custom returned ${value.name}`;
    },
    getLoading(value) {
	return value.loading;
    },
    getValue(value) {
	return value;
    }
}

simple example

const pipeCore = createPipeCore(value, customStart);
await pipeCore
    .getName(name => {
         // name === 'custom returned @pipex/core'
         return '123';
     })
     .pipe<string>(name => {
         // name === '123'
     })
     .getName(name => {
	 // name === 'custom returned @pipex/core'
      })
     .pipeEnd();

use piecePipe

const pipeCore = createPipeCore(value, customStart);
await pipeCore
    .getName((name, piecePipe) => {
        // name === 'custom returned @pipex/core'
        piecePipe
	   .getLoading((loading, _, set) => {
		// loading === false
		// update loading value to true
	        set({ loading: true });
	    })
       return '123';
    })
    .pipe<string>((name, piecePipe) => {
        // name === '123'
        piecePipe
	    .getLoading((loading, _, set) => {
		// loading === true
	    })
     })
     .pipeEnd();

use instance()

const pipeCore = createPipeCore(value, customStart);
const testInstance = async () => {
    await pipeCore
        .instance()
	.getValue(async (_, __, set) => {
	    // update loading to true
	    set({ loading: true });
	    await testNewInstance();
	})
	.pipeEnd();
}
const testNewInstance = async () => {
    await pipeCore
      .instance(true)
      .getValue((_, __, set) => {
        // update name
        set({ name: 'instance @pipex/core' });
      })
      .pipeEnd();
};
await pipeCore
    .getName((name, piecePipe) => {
        // name === 'custom returned @pipex/core'
	piecePipe
	    .getLoading(async (loading, _piecePipe, set) => {
		// loading === false
		// update loading value to true
		await testInstance();
		_piecePipe
		    .getName(_name => {
                       // name === 'custom returned @pipex/core',instance(true) not reference value to source PipeCore
                    })
		    .getLoading(loading => {
		        // loading === true
			// instance always called before _piecePipe, so loading is true
		    })
	    })
     })
     .pipeEnd();

API

createPipeCore(value: Record<string, string>, config: Record<string, (value: Value) => any>): PipeCore

createPipeCore will create one PipeCore. value means the origin Record value source. config means the pipeline start function.

instance(createOneFreshValue?: boolean): PipeCore

instance will create one new pipeline to call. createOneFreshValue means need create one independent PipeCore.

piecePipe: PiecePipeCore

piecePipe means if you do sth in line A, you could use piecePipe to do sth in other line includes line A

pipeEnd(): void;

pipeEnd means call all functions, only called in PipeCore, not in PiecePipeCore

Annotation

  • Both instance() and piecePipe could do sth in other line, the instance() would call before piecePipe in every PipeCore function.

TODO

  • support for React state