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

@webpieces/cloudtasks-client

v0.3.375

Published

Cloud Tasks enqueue client generated from a shared @PubSub API contract (twin of http-client)

Readme

@webpieces/cloudtasks-client

The Cloud Tasks twin of @webpieces/http-client. A @PubSub API contract is shared by the enqueue client and the controller, exactly like RPC — calling a method on the client enqueues a Cloud Task that is later delivered (POST) to the SAME endpoint, where it runs through the full server filter chain.

// one shared contract
@PubSub() @AuthOidc() @ApiPath('/email')
abstract class EmailApi { @Endpoint('/send') sendEmail(r: SendEmailRequest): Promise<void> {…} }

// build the client once (sync); 'email-svc' is the callee's Cloud Run service name
const emailTasks = factory.createPubSubClient(EmailApi, new TaskClientConfig('email-svc'));
// ...or pin a URL lookup cannot describe (other region/project); svcName stays the log name
const other = factory.createPubSubClient(EmailApi, new TaskClientConfig('email-svc', 'https://email.eu.example'));

// producer (inside a request → RequestContext active)
await scheduler.addToQueue(() => emailTasks.sendEmail(req), { dedupName: req.id });
  • ClientCloudTasksFactory.createPubSubClient(Api, TaskClientConfig) — builds the enqueue proxy. It injects a Provider<TaskProxyClient> and calls get() per contract; TaskProxyClient is bound TRANSIENT, so each client gets its own. The delivery URL is resolved at enqueue time from svcName via resolveServiceUrl: a ClientRegistry override wins, else on GCP it is derived from the Cloud Run service name (same project + region, so you maintain no URL table), else (off-GCP, unregistered) it throws. Register non-derivable URLs (localhost, cross-region, non-Cloud-Run) once at startup with ClientRegistry.addMapping(svcName, port) / addUrlMapping(svcName, url)
  • An enqueue outside RequestContext.run(...) throws: a task with no caller trace is a bug
  • CloudTaskScheduleraddToQueue / schedule / cancelJob; carries scheduling options out-of-band so the contract signature stays identical on both sides
  • TaskInvoker (abstract token) with two impls:
    • GcpTaskInvoker — real @google-cloud/tasks delivery (OIDC / shared-secret)
    • InMemoryTaskInvoker — dispatches through the real server filter chain in-process (tests + local dev, no GCP, production parity)