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

@dagger-team/js-dagger-client

v0.2.0

Published

Client library for dagger. Includes worker and Task logging scripts

Downloads

68

Readme

Status Client Libarary

Library used to log dagger task status from within the runtime of the task itself.

Usable by both the job processor client library (also in this repo), and by any consumer of the API (status only dagger customers).

Different levels of integration are allowed, designed for varying levels of customization based on use-case.

Simple, automatic integration:

By just importing the dagger client, and calling init with your API key, dagger will attempt to automatically detect the environment and log task run status to dagger.


const Dagger = require('js-dagger-client');
Dagger.init('apikey');

// or:
Dagger.init('apikey', {integrationName: 'aws_lambda'});

// or:
Dagger.init('apikey', {integration: MyCustomIntegration()}})

Function wrapper:

A function wrapper is provided that will log any call to that function as a new task run. Task run id will be automatically generated, or you can provide a task run id generator via the getTaskRunId parameter.

const Dagger = require('js-dagger-client');
const daggerClient = new Dagger('apikey').statusClient;

const yourTaskFunction = () => {
    console.log('Doing something....')
};

daggerClient.wrap(
    yourTaskFunction, 
    { 
        taskName: 'some task name'
    },
    {
        // or...
        integration_name: 'aws_ecs'
        // or...
        integration: MyCustomIntegration()
    }
);

Fully custom:

Using the daggerClient you can create and update your own task run.

const Dagger, { TaskRunStatusTypes } = require('js-dagger-client');
const daggerClient = new Dagger('apikey');

const yourTaskFunction = () => {
    const task_run = daggerClient.createTaskRun('some task name', 'a unqiue task run id', TaskRunStatusTypes.running, { input: 'Some input' });

    try:
        console.log('Doing something');
        daggerClient.updateTaskRun(task_run, TaskRunStatusTypes.succeeded, { output: 'Some output' });
    catch(err):
        daggerClient.updateTaskRun(task_run, TaskRunStatusTypes.failed, { error: err });
};

yourTaskFunction();