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

kronos-flow

v2.5.40

Published

Base flow implementation

Downloads

35

Readme

npm Greenkeeper semantic-release styled with prettier Build Status bithound codecov.io Coverage Status Known Vulnerabilities GitHub Issues Stories in Ready Dependency Status devDependency Status docs XO code style downloads Commitizen friendly

kronos-flow

A flow is a bunch of steps and the connection between the steps. So a flow is a directed graph. The edges are the connections between the steps. The vertex is the step. A flow has inbound and outbound steps and processing steps. A flow must fulfill the following requirements:

  • It must have a name.
  • It must have a description.
  • It must have at least one inbound step.
  • All the steps must have at least one connection.
  • All steps must be reachable from the inbound steps.

A Flow may also have endpoints which could be connected to the steps. So it is possible to bundle steps in a flow. From the outside the flows acts as a single step.

API

Table of Contents

Flow

Extends Step

This is the flow implementation. It holds all the steps. Declares the following properties: -steps -autostart

Parameters

  • config {Object} The definition used to create the flow
  • owner {Object} owner of the flow

createEndpoints

The flow has no real endpoints. It only has proxies. So just return the configuration

Parameters

  • stepDefinition Object The step configuration

endpointFor

Find endpoint for given expression

Parameters

  • expression string
  • wait boolean for endpoint to become present (deliver a promise)
  • problems string

Returns Endpoint found endpoint

connectEndpoints

set the target endpoints

Parameters

  • stepDefinition

connectRootEndpoints

A flow has only endpoint proxies. These will be replaced by the original endpoints of the sub steps get the original endpoints for the Flow.

name

Returns string 'kronos-flow'

willBeUnregistered

Deletes a flow from the stored flow definitions. If the flow is currently running, it will be stopped first. After it is stopped, it will be deleted.

Parameters

  • flow

Returns Promise returns a promise that is fullfilled when the flow is removed or one that rejects if there is no flow for the given flowName

install

With npm do:

npm install kronos-flow

license

BSD-2-Clause