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

tasks.js

v0.1.2

Published

A declarative, test-driven framework for organizing what you're doing - written in Node.js

Downloads

4

Readme

tasks.js

A declarative, test-driven framework for organizing what you're doing - written in Node.js

DANGER: This README is very incomplete & some of the features outlined here are not yet working. Follow at your own risk!

Getting Started

TDD in your production code

tasks.js is a simple package that pushes a declarative coding style that is very similar to TDD.

There are two main concepts:

Task - an encapsulated, asynchronous function that achieves an end goal (examples: 'Create User', 'Process Order', 'Deploy Code')

Action - an optional method available inside a Task that allows you to annotate the "steps" of a task. Utilizing this method will make your code more readable and makes your errors much easier to hunt-down (more on this later)

Methods

task(name, function)

import { task } from 'tasks.js'

task('Create User', async (action) => {
  action('validate user')
  // ...
  action('save user to db')
  // ...
  action('send welcome email')
  // ...
})

tasks(name, functions)

import { task, tasks } from 'tasks.js'

await tasks([
  task('', async (action) => {
    action('...')
    // ...
    action('...')
    // ...
  }),
  task('', async (action) => {
    action('...')
    // ...
    action('...')
    // ...
  }),
  task('', async (action) => {
    action('...')
    // ...
    action('...')
    // ...
  }),
]/*, { concurrency: Infinity }*/)

Logging

await tasks([
  task('Task #1', async (action) => {}),
  task('Task #2', async (action) => {}),
  task('Task #3', async (action) => {})
], { log: true })
// OUTPUT:
// >> Task #1
// >> Task #2
// >> Task #3

Composition

The ability to nest task() with tasks() opens up some cool concurrency declarations that are both powerful and easy to read:

await tasks([
  task('Task #1', async () => {}),
  task('Task #2', async () => {}),
  tasks('Group #1', [
    task('Group #1 - Task #1', async () => {}),
    task('Group #1 - Task #2', async () => {}),
  ], { concurrency: Infinity }),
  task('Task #3', async () => {}),
], { log: true })
// OUTPUT:
// >> Task #1
// >> Task #2
// >> Group #1 >> Task #1
// >> Group #1 >> Task #2
// >> Task #2

The root-level gets run in-order (default: { concurrency: 1 })

Error Handling

Once you get into the habit of composition then async tracing/error handling comes for-free!

await tasks([
  task('Task #1', async () => {}),
  task('Task #2', async () => {}),
  task('Task #3', async () => {})
])
// throws:
// TaskError:
//
//
//
//
//

Tracing

The hierarchy of task() vs action() is really great debugging/tracing tool if used properly.

Classes

The utility functions above are the main ways you'll be working with this package. However, if you want to extend functionality, create your own subclasses, or are just plain interested in how things work, here's a lower-level view of our core:

Task

The class behind task(...) which is actually just a shortcut for new Task(...)!

import { Task } from 'tasks.js'

new Task('', async () => {
  // ...
})

TaskQueue

The class behind tasks(...) which is actually just a shortcut for new TaskQueue(...)!

import { TaskQueue } from 'tasks.js'

new TaskQueue('', async () => {
  // ...
})

TaskError

A sub-class of Error (native) that uses TaskTrace instead of StackTrace for error-tracing & call-stacks.

import { TaskError } from 'tasks.js'

TaskTrace

This is secretly one of the most useful classes - but you'll likely never need to use it yourself. It is essentially a Stack Trace composed of Task and TaskQueue objects instead of StackFrame objects!

import { TaskTrace } from 'tasks.js'