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

domain-workflow

v0.0.3

Published

Human readable workflows with error handling made easy

Downloads

4

Readme

domain-workflow

Human readable workflows with error handling made easy.

Express your workflows in explicit form so anyone can understand and/or write them:

type ParseStringToNumberError = {
    message: string;
};

type ParseStringToNumber = (_: string) => Either<ParseStringToNumberError, number>;
type NumberProcessor = (_: number) => number;
type NumberFormatter = (_: number) => string;

type FancyWorkflow = Workflow<[ParseStringToNumber, NumberProcessor, NumberFormatter]>;
  • FancyWorkflow is statically validated and it's result will be Either<ParseStringToNumberError, string>.
  • If we mess up your stages inputs and outputs or mix sync/async type your workflow will have never type so you cannot do anything with it.

Write the implementation of the stages elsewhere not to scare/bore the business team then run your workflow by:

const fancyWorkflow: FancyWorkflow = [parseStringToNumber, numberProcessor, numberFormatter];
const fancyWorkflowResult = runWorkflow(fancyWorkflow)("42");
// fancyWorkflowResult is type is Either<ParseStringToNumberError, string>

Don't need to worry if the previous step is an async operation or can fail as all of these are handled automatically so you can focus on writing your stages in separation.

Notes

Read this to understand how Either type works.

This library was inspired by Domain Modeling Made Functional and The Pragmatic Programmer (part about Transforming Programming) books.