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

a_

v0.2.1

Published

Non-blocking, asynchronous helper functions for Node.js

Downloads

10

Readme

Non-blocking utils functions for CPU-bound Node processes

Build Status

Node.js is (sorta) single threaded and optimized for I/O not CPU bound operations.
For large collections and calculation intensive operations functions such as each or map
provided by utility libraries like underscore or lodash can monopolize the CPU, blocking Node's event loop.
Besides spawning child processes, using web workers, etc it makes sense to avoid synchronous fns.

Usage

Install with npm: npm i -S a_
Run unit tests with: npm test
Use in your project:

import _ from 'a_'
// or
const _ = require('a_')

Available Functions

The _ implementations here work similar to underscore's implementations,
but accept a callback or return a promise alternatively:

Each

_.each(collection, iterator, callback)
_.each(collection, iterator)
_.filter(collection, test)
  .then((result) => console.log(result))
  .catch((err) => console.error(err))

Map

_.map(collection, iterator, callback)
_.map(collection, iterator)
  .then((result) => console.log(result))
  .catch((err) => console.error(err))

Filter

_.filter(collection, test, callback)
_.filter(collection, test)
  .then((result) => console.log(result))
  .catch((err) => console.error(err))

Reject

_.reject(collection, test, callback)
_.reject(collection, test)
  .then((result) => console.log(result))
  .catch((err) => console.error(err))

Reduce

_.reduce(collection, reducer, accumulator, callback)
_.reduce(collection, reducer, callback)
_.reduce(collection, reducer, accumulator)
  .then((result) => console.log(result))
  .catch((err) => console.error(err))
_.reduce(collection, reducer)
  .then((result) => console.log(result))
  .catch((err) => console.error(err))

Every

_.every(collection, test, callback)
_.every(collection, test)
  .then((result) => console.log(result))
  .catch((err) => console.error(err))

Some

_.some(collection, test, callback)
_.some(collection, test)
  .then((result) => console.log(result))
  .catch((err) => console.error(err))

DropWhile

Returns a slice of array excluding elements dropped from the beginning.
Elements are dropped until test returns falsey

_.some(collection, test, callback)
_.some(collection, test)
  .then((result) => console.log(result))
  .catch((err) => console.error(err))

EachUntil

Iterates over collection until iterator first returns truthy, returns index or key for value for which iterator returned truthy.

_.eachUntil(collection, test, callback)
_.eachUntil(collection, test)
  .then((result) => console.log(result))
  .catch((err) => console.error(err))

EachWhile

Iterates over collection until iterator first returns falsy, returns index or key for value for which iterator returned falsy.

_.eachWhile(collection, test, callback)
_.eachWhile(collection, test)
  .then((result) => console.log(result))
  .catch((err) => console.error(err))

Contributing

In lieu of a formal style guide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code.