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.io/dagger

v0.15.1

Published

A client package for running [Dagger](https://dagger.io/) pipelines.

Downloads

28,371

Readme

Dagger TypeScript SDK

A client package for running Dagger pipelines.

What is the Dagger TypeScript SDK?

The Dagger TypeScript SDK contains everything you need to develop CI/CD pipelines in TypeScript or Javascript, and run them on any OCI-compatible container runtime.

Install

npm install @dagger.io/dagger --save-dev

Local development

You may want to work on the TypeScript SDK and test it directly on a local node project.

1. Create a new Node project

:warning: Skip this step if you already have a node project

mkdir my-test-ts-project

# Init project (you may use yarn or pnpm)
npm init -y

# Add typescript
npm install typescript ts-node --save-dev

# Init typescript project
npx tsc --init

2. Update project settings

Dagger exports its SDK using type module so you will need to also update your package.json to the same type.

Add or update the field type in your package.json from your project root directory:

npm pkg set type=module

You must also update your tsconfig.json to use NodeNext as module.

"module": "NodeNext"

3. Symlink Dagger local module

Go to the Dagger TypeScript SDK directory and do the following :

cd path/to/dagger/sdk/typescript # go into the package directory
npm link # creates global link

Go back to the root directory of your local project to link the TypeScript SDK.

cd path/to/my_app # go into your project directory.
npm link @dagger.io/dagger # link install the package

:bulb: Any changes to path/to/dagger/sdk/typescript will be reflected in path/to/my_app/node_modules/@dagger.io/dagger.

4. Make your contribution

While making SDK code modification you should watch the input files:

cd path/to/dagger/sdk/typescript # go into the package directory
yarn watch # Recompile the code when input files are modified

You can now import the local Dagger TypeScript SDK as if you were using the official one.

import { connect } from "@dagger.io/dagger"

Documentation

Please visit our documentation for a full list of commands and examples.