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

@cumulus-test/task-debug

v1.0.2-beta.0

Published

A harness for debugging workflows.

Downloads

7

Readme

Task Debug Harness

This package provides an executable that can run a workflow defined in a yml file to aid in development and debugging. The yml file format is the same as the format used for deployments.

The executable parses the yml file to identify the defined workflows and dynamically loads and executes the tasks for the designated workflow. Output from each task is used to construct the message payload for the subsequent task. Be advised that although the tasks are running locally, any calls they make using the AWS SDK (e.g., writing to S3 buckets) will execute in AWS.

This can be run easily in a JS debugger to allow step debugging and examination of internal state within tasks.

Usage

node src/index.js debugg -c <collection-id> -b <s3-bucket> -w <workflow> <config-file>

Where

  • collection-id - ID of the collection defined in the yml config file to use
  • s3-bucket - S3 bucket to be used as a data-source, e.g., git-private
  • workflow - Which step function defined in the yml config file to use
  • config-file - The path to the yml file that defines the configuration for the workflow. Currently this option is ignored and the file test-collections.yml in packages/common/test/config is always used.

Limitations

  • Currently only linear workflows are supported, e.g., no branching, but it should be pretty simple to add branching support later.
  • Because of the dynamic loading of tasks it is recommend to use node 8 without transpiling when debugging to avoid the need to generate and deal with source maps