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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@effectionx/context-api

v0.2.1

Published

Often called "Algebraic Effects" or "Contextual Effects", Context apis let you access an operation via the context in a way that it can be easily (and contextually) wrapped with middleware.

Readme

Context Apis

Often called "Algebraic Effects" or "Contextual Effects", Context apis let you access an operation via the context in a way that it can be easily (and contextually) wrapped with middleware.


Let's say that you want to define a log operation that behaves differently in different context. The basic form will just log values to the console.

// file logging.ts
import { createApi } from "@effectionx/context-api";

// create the `logging` api. By default, it just logs to the console.
const logging = createApi<Logging>(
  "logging",
  function* log(...values: unknown[]) {
    console.log(...values);
  },
);

// export the logging operations.
export const { log } = logging.operations;

Now you can use the logging api wherever you want:

import { log } from "./logging.ts";

export function* op() {
  yield* log(`I am in an operation`);
}

However, use can use the around function to wrap middleware around your logging operation. This lets you do stuff like silence logging, or even to re-route it somewhere else than from the console completely.

import { logging } from "./logging.ts";

function* initCustomLogging(externallogger) {
  yield* logging.around({
    *log(...values, next) {
      externalLogger.log(...values);
      // since we override the logger entirely, we do not invoke next.
    },
  });
}

The best part is that the middleware is only in effect inside the scope in which it is installed.

Middleware can be useful for automatic instrumentation. For example, let's assume that fetch was a an api called fetching:

import { fetch, fetching } from "./fetching.ts";

function* instrumentFetch(tracer) {
  yield* fetching.around({
    *fetch(...args, next) {
	  try {
	    tracer.begin("fetch", args),
		return yield* next(...args);
	  } finally {
	    tracer.end("fetch", args);
	  }
	}
  })
}

or mocking inside test cases:

import { fetch, fetching } from "./fetching.ts";

function* useMocks() {
  yield* fetching.around({
    *fetch(...args, next) {
      if (args[0] === "/my-path") {
        return new MockResponse("my-path");
      } else {
        return yield* next(...args);
      }
    },
  });
}