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

take-n-pipe

v1.1.2

Published

Simple tool to seamlessly chain code execution.

Downloads

3,069

Readme

take 'n pipe

Simple tool to seamlessly chain code execution.

MIT License

Code sample

Why take 'n pipe?

  • Easy way to process data in a linear and readable manner.
  • You are not polluting current scope with unnecessary, single use variables.
  • Catch errors predictably, at any point in a chain, instead of nesting multiple try-catch clauses.
  • You can start processing your data synchronously and proceed to the asynchronous context at any point.

Features

  • 😝 Ridiculously simple.
  • ⚙️ Sync & async context.
  • 📦 Distributions in ESM and CommonJS standards.
  • 📘 Full TypeScript support.
  • 🔋 Bateries included - no dependencies.
  • 🧪 Well tested with Jest.

Installation

  # With NPM
  npm install take-n-pipe

  # With Yarn
  yarn add take-n-pipe

The way you go

Sync pipes

  1. Take any input data.
take(data)
  1. Transform data with the pipe(...) method as many times as you want.
.pipe((data: object) => {...})
  1. [Optionally] Catch errors with catch(...) method at any time.
.catch((error: unknown) => {...})
  1. Obtain results.
.get()

Async pipes

  1. Take any input data.
takeAsync(promise)
  1. Transform data with the pipeAsync(...) method as many times as you want.
.pipeAsync(async (data: object) => {...})
  1. [Optionally] Catch errors with catchAsync(...) method at any time.
.catchAsync((error: unknown) => {...})
  1. Obtain results as a Promise.
.toPromise()

Mixed pipes

  1. Start within sync context, take any input data.
take(data)
  1. Being in sync context transform data with the pipe(...) method as many times as you want.
.pipe((data: object) => {...})
  1. Call the pipeAsync(...) method to proceed to async context.

By calling the pipeAsync(...) method on a synchronous chain, you turn it into an asynchronous chain from that point on.

This is a one-way ticket, there is no way to go back to the synchronous chain anymore.

.pipeAsync(async (data: object) => {...})
  1. Obtain results as a Promise.
.toPromise()

Examples

https://github.com/IdkMan2/take-n-pipe/blob/8a01d6223fa37f061db6074f09c7dd522d13e758/tests/examples/sync-pipes.ts#L14-L43

https://github.com/IdkMan2/take-n-pipe/blob/8a01d6223fa37f061db6074f09c7dd522d13e758/tests/examples/mixed-pipes.ts#L29-L66