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

@alpha-lambda/tasks

v1.0.0

Published

simple task framework

Downloads

345

Readme

@alpha-lambda/tasks

This is a simple task management library, for use in Lambda, connected to SQS and maybe Kinesis.

Usage

First, define tasks:

tasks.js

const tasks = require('@alpha-lambda/tasks');

module.exports = tasks([
    {
        type: 'foo',
        schedule(context, tasks) {
            // call SQS, Kinesis, etc.
        },
        execute(context, tasks, Task) {
            // perform the work that the task defines
            // Task is provided so you can schedule new sub-tasks if needed
        },
        validate(task) {
            // optional, verify that the task details match some schema you have
        },
        format(detail) {
            // optional, called before validate
        },
    },
]);

Schedule some tasks:

const Task = require('./tasks');

module.exports.scheduleTasks = async (event, context) => {
    // context is passed forward schedule() in each definition
    await Task.schedule(context, [
        new Task('foo'),
        // this would throw, because 'bar' is not defined above
        new Task('bar', { foo: true }),
    ]);
};

Then, in some other code, such as a Lambda hooked up to SQS as an event source:

module.exports.handler = async (event, context) => {
    const messages = ...
    const tasks = messages.map(message => {
        const parsed = JSON.parse(message);
        return Task.fromJSON(parsed);
    });

    await Task.execute(context, tasks);
};