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

@othree.io/scribe

v3.0.0

Published

Scribe

Downloads

18

Readme

@othree.io/scribe

Function wrapper with lifecycle hooks. Attach callbacks to react when a function is called, completes, or fails — useful for logging, metrics, side effects, or any middleware-style behavior. Includes automatic duration measurement.

Returns Optional<T> from @othree.io/optional, capturing errors instead of throwing.

Install

npm install @othree.io/scribe

Usage

Sync

import { scribe } from '@othree.io/scribe'

const result = scribe({
    now: Date.now,
    fn: (name: string, count: number) => `${name} x${count}`,
    transcribeInput: (...args) => console.log('Input:', args),
    transcribeOutput: (output, durationMs) => console.log('Output:', output, `(${durationMs}ms)`),
    transcribeError: (error, durationMs) => console.error('Error:', error, `(${durationMs}ms)`)
})('Alice', 3)

result.get() // 'Alice x3'

Async

import { scribeAsync } from '@othree.io/scribe'

const result = await scribeAsync({
    now: Date.now,
    fn: async (id: string) => fetchUser(id),
    transcribeInput: (id) => logger.info('Fetching user', { id }),
    transcribeOutput: (user, durationMs) => logger.info('Fetched user', { user, durationMs }),
    transcribeError: (error, durationMs) => logger.error('Fetch failed', { error, durationMs })
})('user-123')

result.map(user => user.name).orElse('Unknown')

Minimal (no hooks)

All transcribe callbacks are optional. At minimum, provide now and fn:

const result = scribe({
    now: Date.now,
    fn: (x: number) => x * 2
})(21)

result.get() // 42

Error handling

Errors thrown by fn are captured in the Optional rather than re-thrown:

const result = scribe({
    now: Date.now,
    fn: () => { throw new Error('boom') },
    transcribeError: (error, durationMs) => logger.error(error.message, { durationMs })
})()

result.isEmpty    // true
result.getError() // Error('boom')

As middleware / side effects

The hooks are not limited to logging. Use them for any side effect that should run at a specific point in the function lifecycle:

const result = scribe({
    now: Date.now,
    fn: (orderId: string) => processOrder(orderId),
    transcribeInput: (orderId) => metrics.increment('orders.started', { orderId }),
    transcribeOutput: (order, durationMs) => {
        metrics.histogram('orders.duration', durationMs)
        cache.set(order.id, order)
    },
    transcribeError: (error) => alerting.notify('Order processing failed', error)
})('order-456')

API

scribe<A, T>(deps: ScribeDeps<A, T>) => (...args: Array<A>) => Optional<T>

Wraps a synchronous function.

scribeAsync<A, T>(deps: ScribeAsyncDeps<A, T>) => (...args: Array<A>) => Promise<Optional<T>>

Wraps an asynchronous function.

Deps

| Property | Type | Required | Description | |---|---|---|---| | now | () => number | yes | Clock function for duration measurement (e.g. Date.now) | | fn | (...args) => T or (...args) => Promise<T> | yes | The function to instrument | | transcribeInput | (...args) => void | no | Hook called with the original arguments before fn executes | | transcribeOutput | (output: T, durationMs: number) => void | no | Hook called with the return value and duration when fn succeeds | | transcribeError | (error: Error, durationMs: number) => void | no | Hook called with the error and duration when fn fails |

Lifecycle

  1. Record startTime via deps.now()
  2. Call transcribeInput with the arguments (if provided)
  3. Execute fn (wrapped in Try / TryAsync)
  4. Compute durationMs via deps.now() - startTime
  5. On success: call transcribeOutput with the result and duration
  6. On error: call transcribeError with the error and duration
  7. Return Optional<T> containing the result or the captured error