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

iox

v1.0.0

Published

An exploration of the Haskell IO patterns, in pure Javascript.

Readme

iox

An exploration of the Haskell IO patterns, in pure Javascript.

Build Status

Install: npm install --save iox

Try it out live: https://runkit.com/pokle/iox-example

What?

Instead of passing dependencies to your functions, instead arrange for them return:

  • A description of what IO operation they would like carried out.
  • What to do after the IO operation has completed.

For example:

function lowerCaseInput() {
    return { io: 'read-file', file: '/etc/hosts', then: (str) => str.toLowerCase() }
}

So how do you run this? Check out the full example at examples/lowercase-file.js

Why?

Functions that perform input & output operations are usually quite hard to test. (As opposed to pure functions)

  • You might use mocking techniques - painful.
  • You might use dependency injection (to inject mocks and genuine implementations)

Dependency injection can be problematic because you have to pass your dependencies all the way through your function call hierarchy. With iox, your functions compose easier because you're never passing down dependencies.

Influences

  • Haskell IO Monad
  • Purescript Effects, Aff, and IO
  • funfix's IO type (https://github.com/funfix/funfix)
  • From dependency injection to dependency rejection (http://blog.ploeh.dk/2017/01/27/from-dependency-injection-to-dependency-rejection/)

Release process

npm test
npm run build 
npm version major | minor | patch...
git push
npm publish