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

@reggi/journey

v1.0.192

Published

Reduce based functional flow control

Readme

@reggi/journey

npm i @reggi/journey

Why

journey allows you to design a functional flow, it is a reducer for functions with the goal of storing all values along the way into one big object, but sill allowing for a returnable value

const {journey} = require('@reggi/journey')

const cleanGreeting = (greeting) => (greeting === 'hi') ? 'Hello' : greeting

const helloWorld = journey((greeting, name) => [
  () => ({greeting, name}), // put greeting and name into the object to use
  ({greeting}) => ({cleanGreeting: cleanGreeting(greeting)}), // here we create a new property and return it it gets added to the object,
  ({cleanGreeting, name}) => ({message: `${cleanGreeting} ${name}`}) // here we have access to `name` and `cleanGreeting`, all we need
])

// Here we can call this function and get the entire function back

console.log(helloWorld('hi', 'Thomas')) // => {greeting: 'hi', name: 'Thomas', cleanGreeting: 'Hello', message: 'Hello Thomas'}

Now if we only wanted message to be returned, we would do this:

const {journey} = require('@reggi/journey')

const cleanGreeting = (greeting) => (greeting === 'hi') ? 'Hello' : greeting

const helloWorld = journey((greeting, name) => [
  () => ({greeting, name}), // put greeting and name into the object to use
  ({greeting}) => ({cleanGreeting: cleanGreeting(greeting)}), // here we create a new property and return it it gets added to the object,
  ({cleanGreeting, name}) => ({message: `${cleanGreeting} ${name}`}) // here we have access to `name` and `cleanGreeting`, all we need
], {return: 'message'})

// Here we can call this function and get just `message` back

console.log(helloWorld('hi', 'Thomas')) // => 'Hello Thomas'

// But journey also provides us another function, if we call `.journey` we get the entire object back again, even though we added `{return: message}`.

console.log(helloWorld.journey('hi', 'Thomas')) // => {greeting: 'hi', name: 'Thomas', cleanGreeting: 'Hello', message: 'Hello Thomas'}

As you can see all variables declared in the flow are accessable at the end of the function. This is very valuable, because nothing is lost, and everything is accessable.

Async functions work as well

const {journey} = require('@reggi/journey')
const fs = require('fs')
const util = require('util')
const fsRead = util.promisify(fs.readFile)

const cleanGreeting = async (greeting) => (greeting === 'hi') ? 'Hello' : greeting

const helloWorld = journey((greeting, name) => [
  () => ({greeting, name}), // put greeting and name into the object to use
  async ({greeting}) => ({cleanGreeting: await cleanGreeting(greeting)}), // here we create a new property and return it it gets added to the object,
  ({cleanGreeting, name}) => ({message: `${cleanGreeting} ${name}`}) // here we have access to `name` and `cleanGreeting`, all we need
])

helloWorld('hi', 'Thomas')
  .then(v => console.log(JSON.stringify(v))) // {"greeting":"hi","name":"Thomas","cleanGreeting":"Hello","message":"Hello Thomas"}
  .catch(console.log)

Options

The second paramater here is objects that change the essential flow.

hook

const {journey} = require('@reggi/journey')

const cleanGreeting = (greeting) => (greeting === 'hi') ? 'Hello' : greeting

const helloWorld = journey((greeting, name) => [
  () => ({greeting, name}), // put greeting and name into the object to use
  ({greeting}) => ({cleanGreeting: cleanGreeting(greeting)}), // here we create a new property and return it it gets added to the object,
  ({cleanGreeting, name}) => ({message: `${cleanGreeting} ${name}`}) // here we have access to `name` and `cleanGreeting`, all we need
], {hook: (acq, result) => console.log(result)})

console.log(helloWorld('hi', 'Thomas'))

// { greeting: 'hi', name: 'Thomas' }
// { cleanGreeting: 'Hello' }
// { message: 'Hello Thomas' }
// { greeting: 'hi',
//   name: 'Thomas',
//   cleanGreeting: 'Hello',
//   message: 'Hello Thomas' }

This will allow us to log each step allong the way.