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

conducer

v0.0.2

Published

Minimal tools for creating rules with conditions using simple reducers.

Downloads

5

Readme

Conducer

Minimal tools for creating rules with conditions using simple reducers. Conditions are pure functions, so there's no side-effects. Facts must have everything needed by the conditions.

Build Status

Tools:

They return a single condition function which expects the facts as argument in order to return a boolean.

every([ condition, conditionOne, conditionTwo ])

Every condition (all conditions) must be true.

notEvery([ condition, conditionOne, conditionTwo ])

Every condition can't be true.

some([ condition, conditionOne, conditionTwo ])

Some condition must be true.

notSome([ condition, conditionOne, conditionTwo ])

Some condition can't be true.

Examples:

Simple:

import { every, some } from 'conducer'

export const hasRole = role => ({ user }) => user.roles.some(role)
export const isActiveUser = ({ user: { status } }) => status

const canEditComments = every([
  isActiveUser,
  some([
    hasRole('admin'),
    hasRole('moderator'),
  ])
])

const facts = { user: { status: true, roles: ['moderator', 'admin'] } }

if (canEditComments(facts)) {
  // Give access to edit comments.
}
else {
  // Denied access to editing comments.
}

Using the when() chaining function to avoid if conditions:

import { every, some, when } from 'conducer'

// ... same as above.

when(canEditComments(facts))
  .do(() => {
    // Give access to edit comments.
  })
  .else(() => {
    // Denied access to editing comments.
  })

Usage:

LICENSE

MIT