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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@terella/action-framework

v0.0.3

Published

DI-friendly GitHub Actions framework with terella-action CLI for init and build

Readme

@terella/action-framework

DI-friendly GitHub Actions you can unit-test. Scaffold with terella-action, ship with npm run build.

Get started

bunx @terella/action-framework init my-action --yes --workflow
cd my-action && bun install
bun run build

That’s a runnable Node 20 action. action.yml points at dist/index.js; --workflow also writes .github/workflows/<name>.yml that uses: ./.

The whole action

init writes a workflow like this:

import {
  ACTION_COMPONENTS,
  type ActionRuntime,
  Inject,
  InjectableWorkflow,
} from "@terella/action-framework";

@InjectableWorkflow()
export class MyActionWorkflow {
  constructor(
    @Inject(ACTION_COMPONENTS.actionRuntime)
    private readonly runtime: ActionRuntime,
  ) {}

  async run(): Promise<void> {
    const name = this.runtime.getInput("name") || "World";
    this.runtime.info(`Hello, ${name}!`);
    this.runtime.setOutput("message", `Hello, ${name}!`);
  }
}

Wire composition in src/index.ts, change inputs in action.yml, rebuild.

Ship many

Same layout every time — good for fleets and reviewable diffs:

for name in sync-metadata notify-slack prune-branches; do
  bunx @terella/action-framework init "actions/$name" --yes --name "$name" \
    --description "Automation: $name"
done

Every package gets bun run buildterella-action build (requires Bun).

Flags: --name, --description, --author, --yes, --force, --no-sample-input, --workflow.

Wire it up

# action.yml (generated)
runs:
  using: "node20"
  main: "dist/index.js"

With --workflow, init also writes:

# .github/workflows/my-action.yml
name: my-action
on:
  push:
  pull_request:
  workflow_dispatch:
jobs:
  run:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: ./
        with:
          name: Alice

Test without GitHub

import {
  MockActionRuntime,
  createActionComposition,
  runComposedAction,
} from "@terella/action-framework";
import { MyActionWorkflow } from "./workflow.js";

const runtime = new MockActionRuntime();
runtime.inputs.name = "Tester";

await runComposedAction(
  createActionComposition(
    { githubContext: { repo: { owner: "o", repo: "r" } }, dependencies: {} },
    { runtime },
  ),
  MyActionWorkflow,
);

expect(runtime.outputs.message).toBe("Hello, Tester!");

CLI

terella-action init [dir] [options]   # add --workflow for .github/workflows
terella-action build [entry=src/index.ts] [outdir=dist] [--minify]
terella-action --help

build bundles the entrypoint for Actions and writes dist/package.json with "type": "module".

Examples

See examples/ for exec, GitHub client, custom services, and local-action patterns.

Features

  • ActionRuntime — inputs, outputs, logs (swap for MockActionRuntime in tests)
  • DI composition@InjectableWorkflow / @InjectableService via @di-framework/core
  • terella-action — init + build for one action or many