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

@pumped-fn/lite-extension-logging

v1.0.1

Published

Execution-scoped logging extension for @pumped-fn/lite with tag-injected sinks

Downloads

441

Readme

@pumped-fn/lite-extension-logging

Execution-scoped logging for @pumped-fn/lite.

The extension is static composition. Runtime backend choice is a tag. Install logging.extension() to get automatic flow logs when requested, and resolve the logging.logger resource when application code needs explicit logs.

Migration to 1.0.0

Install 1.0 with Lite 6:

npm install @pumped-fn/lite@^6.0.0 @pumped-fn/lite-extension-logging@^1.0.0
import { createScope, flow } from "@pumped-fn/lite"
import { logging } from "@pumped-fn/lite-extension-logging"

const records = logging.memory()
const scope = createScope({
  extensions: [logging.extension()],
  tags: logging.runtime({
    sinks: [records],
    level: "info",
    flow: "errors",
    fields: { service: "worker" },
  }),
})

const run = flow({
  name: "run",
  deps: { logger: logging.logger },
  factory: (_ctx, { logger }) => {
    logger.info("run.accepted")
  },
})

Runtime

logging.runtime(...) carries backend policy:

| Option | Role | | --- | --- | | sinks | Log destinations. A backend package should adapt to this interface. | | level | Minimum level: debug, info, warn, or error. | | flow | Automatic flow logs: none, errors, or all; payloads stay out of log records. | | fields | Runtime fields merged into every record. | | source | Source override for records created inside this runtime. | | redact | Field mapper before a record reaches sinks. | | failure | isolate keeps app execution moving; throw makes sink failure fail execution. | | onError | Observes sink failures without hidden swallowed errors. | | now / id | Deterministic clock and id hooks for tests and runtimes. Override id for scoped ids. |

The logging.logger resource is execution-owned and flushes sinks on context close. logger.child(fields) adds local fields without changing the runtime tag. The built-in logging.memory() sink is for tests and local inspection; size() returns buffered record count. OpenTelemetry logs and OTLP collectors are adapter targets for Logging.Sink; this package does not import or ship those backends. Use @pumped-fn/lite-extension-logging-pino when the runtime sink should write records to Pino.


Part of pumped-fn — start with the docs or the mental model.