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

@saber2pr/fp

v0.0.7

Published

> functional programing in async & sync.

Downloads

8

Readme

@saber2pr/fp

npm

functional programing in async | sync | lazy.

# from npm
npm install @saber2pr/fp

# from github
git clone https://github.com/Saber2pr/fp.git

Why

If you often program with node.js, there will be some bad cases in async, like this:

const contents = await Promise.all(
  ['./1.txt', './2.txt'].map(async file_name => ({
    content1: await readFile(file_name).then(buffer => buffer.toString()),
    content2: await readFile(file_name).then(buffer => buffer.toString())
  }))
)

then you get a bad result, the contents.content1 and contents.content2 is a Promise

How to deal with it?

Now, there is a function named async_map to it:

const contents = async_map(['./1.txt', './2.txt'], async file_name => ({
  content1: await readFile(file_name).then(buffer => buffer.toString()),
  content2: await readFile(file_name).then(buffer => buffer.toString())
}))

you will get a result and the contents.content1 and contents.content2 is the correct type "string".

what's more...

API

compose

pipe

setter

async_reduce

async_reduceRight

async_compose

async_pipe

async_setter

async_forEach

async_filter

async_intercept

async_map

*range

*map

*filter

*reduce

toIt

from


start

npm install
npm start

npm test

Author: saber2pr


develope and test

you should write ts in /src

you should make test in /src/test

export your core in /src/index.ts!