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

@temporalio/common

v1.25.0

Published

Common library for code that's used across the Client, Worker, and/or Workflow

Readme

@temporalio/common

NPM

Part of Temporal's TypeScript SDK (see docs and samples).

Common library for code that's used across the Client, Worker, and/or Workflow:

Payload Caching

Experimental. Clients and Workers can cache External Storage payloads, so a payload already in the cache is not retrieved from its storage driver again. Caching is off by default. The SDK exposes a generic PayloadCache interface and an in-memory implementation, InMemoryPayloadCache, exported from @temporalio/client and @temporalio/worker. Pass a payload cache to clients and workers to enable caching, or pass the same cache to both to share it:

import { Client, InMemoryPayloadCache } from '@temporalio/client';
import { Worker } from '@temporalio/worker';

const payloadCache = new InMemoryPayloadCache({
  maxTotalBytes: 128 * 1024 * 1024,
  maxEntries: 20_000,
});

const client = new Client({ payloadCache });
const worker = await Worker.create({ taskQueue, workflowsPath, payloadCache });

n.b. The cache is a best-effort optimization.

External Storage

External Storage caches the final encoded Payload given to a storage driver. Cache hits do not call the storage driver. The reference payload claim data is used to construct the cache key through the following steps:

  1. UTF-8 encode the driver name and every claim key and value without normalization.
  2. Sort claim keys by unsigned lexicographic order of their UTF-8 bytes.
  3. Encode each string as its ASCII base-10 UTF-8 byte length, :, then the original string.
  4. Prefix the key with v0/temporal/extstore/.
  5. Concatenate the encoded driver name, then each sorted claim key and value.

For driver aws-s3 and claim data { bucket: "abc", key: "1" }, the key is:

v0/temporal/extstore/6:aws-s36:bucket3:abc3:key1:1