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

simple-workflows

v0.1.0-beta14

Published

Workflows as code in TypeScript

Downloads

67

Readme

simple-workflows

Simple repeatable workflows and activities as code.

Goals:

  • Repeatable long running programs.
  • Close to zero dependencies.
  • No extra infrastructure requirements.
  • Statically typed.

History/state can be serialized to:

  • Memory
  • File System
  • Azure Table and Blob Storage

Inspired by Azure Durable Function and Temporal.

Activities

All activities is just normal functions that return promises, but must be idempotent and both args and return value must be serializable.

Example activity:

export async function greet(name: string): Promise<string> {
    return `Hello, ${name}!`;
}

Workflows

Workflows is build by activities. When activities is used in workflows, they must be passed to the proxyActivities function:

import * as activities from '../activities';
import { proxyActivities } from "simple-workflows";

const { greet } = proxyActivities(activities, {});

export async function greetWorkflow(name: string): Promise<string> {
    return await greet(name);
}

Getting started

import { WorkflowWorker } from "simple-workflows";

const worker = WorkflowWorker.getInstance();

const handle = await worker.start(greetWorkflow, {
    args: ["debug"],
    workflowId: "debug",
});

console.log(`Started workflow ${handle.workflowId}`);

let result = await handle.result();

Custom serialization

By default standard JSON serialization is used, the serialization can be customized by setting serializer on the store eg.:

import superjson from 'superjson';

const worker = WorkflowWorker.getInstance();
const store = new DurableFunctionsWorkflowHistoryStore({
  connectionString: "UseDevelopmentStorage=true",
  serializer: superjson,
});
worker.store = store;

Limitations

  • Workflows & activities is executed in the current process
  • Workflows & activities will not forcefully be stopped on timeout