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

monadanator

v2.0.0

Published

When you want to make things pure and functional.

Downloads

3

Readme

Monadanator

When you want to make things pure and functional.

Usage

Container

Basic container that both a functor and a monad. It responds to map and flatMap. In addition, it also responds to of and ap.

of describes a pointed monad where as ap describes an applicative monad.

examples

import { container } from 'monadanator'

container(3)
  .map(three => three * 2)
  .flatMap(six => container.of(2)
    .map(two => two * six)
  )
  .map(twelve => console.log(twelve))

container
  .of(x => console.log(x))
  .ap('something that will get logged')
  .ap(container.of('another thing that will be logged'))

IO

provides a function that acts just like container, but implements the expected IO Monad behaviour.

The only difference between an IO monad and a Container monad is that an IO monad waits to execute any calls to map, flatMap or ap. These calls will only be run when perform is called.

examples

import { io } from 'monadanator'

const helloWorld = io.of(window)
  .map(w => window.alert('hello world')) // no alert

helloWorld.perform() // alert's hello world

alternatively, you could use the run helper function

import { io, helpers: { run } } from 'monadanator'

const helloWorld = io.of(window)
  .map(w => window.alert('hello world'));

const append = io.of(document)
  .map(doc => document.body.appendChild('hello!'))

run(
  helloWorld,
  append
) //alerts hello world & appends child

Maybe

Maybe represents a point in your program where things could go wrong. It works exactly like a container, except when it receives a value of undefined or null. At which point, map, flatMap and ap will stop running.

There is also error method that will only run if the value contained within the Maybe monad is either undefined or null

examples

import { maybe } from 'monadanator'
  maybe.of(true)
    .map(x => !x)
    .map(x => undefined) // everything past this point will never run
    .flatMap(x => maybe.of(3).map(x => * 2))
    .map(six => console.log(six))
    .error(_ => console.log('something went wrong')) // runs because the monad contains undefined