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

@opuscapita/fsm-workflow-task-manager

v3.0.1

Published

Task manager for FSM workflow

Downloads

7

Readme

FSM Task Manager

badge-npm-version NPM Downloads

FSM Task(Work) Manager is an extension to finite state machine. It manages existing tasks (stateful objects, e.g. invoice) within the lifecycle specified in Finite State Machine definition.

Usage

Machine(workflow) definition

An example could be found here

Task(process) Manager

const machine = new Machine({
  machineDefinition: new MachineDefinition({schema,actions,conditions}),
  context
});

const taskManager = new TaskManager({
  machine: machine,
  search: search,
  update: update
});

//function that return promise that is resolved with task list
function search(searchParams) {
  return new Promise((resolve, reject) => {
    setTimeout(() => {
      resolve([{status: ''}, {status: ''}]);
    }, 500)
  })
};

//function that return promise that is resolved after object saving
function update(object) {
 return new Promise((resolve, reject) => {
  //some hard-working persistent saving code
  resolve();
 })
};

Starting the process

After configuration there is only one thing left behind - to start task list monitoring.

taskManager.run({ timeout: 1000 });

timeout argument indicates the frequency of calling search action and checking for available automatic event / sending events (in case found auto-transitions);

Stopping the process

If the time has come to kill the process, you have to do the next:

taskManager.stop();

This method return true/false in case of correct/incorrect process finish, correspondingly.

Getting ongoing/stopped process statistic

Sometime you may need to get the process statistic (currently available values are: machine name, start & end timestamps)

taskManager.processCache

This field is an object with next signature:

{<timer_descriptor> : {
  <name>,
  <started>,
  <finished>
}}

TBD: increase process cache notation usability TBD: add 1 by 1 event sending queue

Sending event to object with TaskManager

You might need an ability to send event to an object with further saving. If you configured TaskManager properly and it knows how to save objects, next two code snippets do the same:

//passed as constructor arg to TaskManager
const update = (object) => {
  <some async object update code>
  return Promise
};
machine.sendEvent({object, event, request}).then(({object}) => {
  return update(object);
})

//----equals---

taskManager.sendEvent({object, event, request})

Starting workflow with TaskManager

Also you might want to start the workflow with further object saving. If you configured TaskManager properly and it knows how to save objects, next two code snippets do the same:

//passed as constructor arg to TaskManager
const update = (object) => {
  <some async object update code>
  return Promise
};
machine.start({object}).then(({object}) => {
  return update(object);
})

//----equals---

taskManager.start({object})