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

@tsed-plus/temporal

v2.0.0

Published

Extends the Ts.ED framework with the functionality to define temporal.io activities within a service class and to start a worker that can execute workflows

Readme

Ts.ED Plus Temporal

Support for Temporal in your Ts.ED application.

Contents

Prerequisite

If you have not already, familiarize yourself with the Ts.ED framework and the concepts around Temporal

Getting Started

Install Module

# npm
npm install @tsed-plus/temporal

# yarn
yarn add @tsed-plus/temporal

Write Activities

Annotate your class with @Temporal and the activity methods with @Activity, given an optional name. You can use your injected services within the activity method.

import { Activity, Temporal } from '@tsed-plus/temporal';
import { GreetingService } from './GreetingService';

@Temporal()
export class GreetingActivities {
  constructor(private greetingService: GreetingService) {}

  @Activity({ name: 'greeting' })
  async greeting(name: string): Promise<string> {
    return this.greetingService.greeting(name);
  }
}

Optional, create an interface for your activities to use it later for your workflows

interface IGreetingActivity {
  greeting(name: string): Promise<string>;
}

export type Activities = IGreetingActivity;

Write Workflows

Workflows are regular functions and do not interact directly with Ts.ED. Just the earlier created interface is used for type-safety.

import { proxyActivities } from '@temporalio/workflow';
import { Activities } from '../activities';

export async function example(name: string): Promise<string> {
  const { greeting } = proxyActivities<Activities>({
    startToCloseTimeout: '1 minute',
  });

  return await greeting(name);
}

Start a Workflow

Inject the TemporalWorkflowClient in a service/controller of your choice and call start. You can specify the workflow name by string like above or also import the function and pass it to have type-safety for the arguments.

Also check out the Temporal client documentation here about more cool things you can do with the Workflow Clients.

import { nanoid } from 'nanoid';
import { Controller } from '@tsed/di';
import { Get } from '@tsed/schema';
import { QueryParams } from '@tsed/platform-params';
import { TemporalWorkflowClient } from '@tsed-plus/temporal';

@Controller('/')
export class HelloWorldController {
  constructor(private workflowClient: TemporalWorkflowClient) {}

  @Get('/')
  async get(@QueryParams('name') name?: string) {
    const workflow = await this.workflowClient.start('example', {
      args: [name || 'World'],
      taskQueue: 'hello-world',
      workflowId: 'workflow-' + nanoid(),
    });
    return workflow.result();
  }
}

Start a worker

The workflows and activities won't get executed until you start a worker.

The most tricky part is the workflowsPath parameter. This is the path of the file where the workflows are defined. The file is automatically loaded when the worker is started and internally bundled with webpack. Read more about it here.

import { bootstrapWorker } from '@tsed-plus/temporal';
import { Server } from './app/Server';

const worker = await bootstrapWorker(Server, {
  worker: {
    taskQueue: 'hello-world',
    workflowsPath: require.resolve('./temporal'),
  },
});
await worker.run();

Example

Look at the puzzle pieces explained above in a working example application.