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

@clausehq/flows

v0.1.14

Published

Main Flows Engine

Downloads

22

Readme

Flow engine

This is a generic flow execution enginee.

The engine is parameterized with a set of transforms and types.

Transforms and types need to have the right structure (npm packages exporting an object with the proper fields).

The engine can be instantiated with:

const engine = require('@clausehq/core-flows');
const registry = {
  transforms: [
    { name: <TRANSFORM_NAME>, package: <TRANSFORM_PATH> },
    ...
  ],
  types: [
    { name: <TYPE_NAME>, package: <TYPE_PATH> },
    ...
  ],
};
const myEngine = engine(registry);

The flow engine API allows you to invoke a flow:

const result = myEngine.invoke(flow, context, request);

Where:

  • flow is the flow (ALMOST! it still has a few bits pre-hydrated, but very close now)
  • context is the invokation context (e.g., secrets, previous steps etc)
  • request is the input of the flow