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

@minamorl/darkcore

v0.1.0

Published

A small tagged-data effect interpreter with explicit handlers.

Downloads

39

Readme

@minamorl/darkcore

A standalone TypeScript effect interpreter built from small tagged data and an explicit handler map. It has no runtime dependencies, global HKT registration, typeclass catalog, operator overloading, or per-transformer API.

Install

npm install @minamorl/darkcore

Effects

Effect<A> is a type-only export. A value is either Pure, which is closed, or one Op carrying a string tag, its input, and onReturn. The continuation only constructs the next node; handlers perform the effects.

import {
  op,
  pure,
  run,
  type Effect,
  type HandlerMap,
} from "@minamorl/darkcore";

const program: Effect<number> = op("read", { key: "answer" }, (value: number) =>
  op("add", { left: value, right: 1 }, (sum: number) => pure(sum)),
);

const handlers: HandlerMap = {
  read: ({ key }: { key: string }) => (key === "answer" ? 41 : 0),
  add: ({ left, right }: { left: number; right: number }) => left + right,
};

run(program, handlers); // 42

fold and foldAsync add the terminal onReturn algebra. run and runAsync return the terminal value unchanged. Both interpreters replace the current node in a loop, so long operation chains are stack safe. A sync run rejects a handler that returns a promise.

The complete runtime function surface is:

  • pure, op
  • fold, run
  • foldAsync, runAsync
  • scoped, scopedAsync

The directly required type surface is Effect, HandlerMap, and ScopeExit.

Owned resources

scoped(acquire, use, release) keeps acquisition, use, and release in one call. Once acquisition succeeds, release observes a Success or Error exit on normal completion, callback return, or throw.

scopedAsync provides the same rule for promise-returning callbacks. JavaScript promises cannot be forcibly cancelled; cancellation within the language guarantee is cooperative rejection (for example AbortError), which follows the error release path.

Errors

Interpreter and scope failures are Error instances with the stable envelope fields code, message, details, and ULID-shaped trace_id. Error details contain only names/messages for nested failures, never raw stacks. The library emits no logs and reads no secrets.