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

@rnw-community/log-decorator

v2.0.3

Published

Universal log method decorator with pluggable transport and pre/post/error hooks. Built on TypeScript's experimentalDecorators. Zero framework dependencies.

Readme

Log Decorator

Universal method decorator with pre / post / error logging hooks and a pluggable transport. Built on @rnw-community/decorators-core. Handles sync, Promise, and Observable return types automatically. TypeScript experimentalDecorators.

npm version npm downloads

When each hook fires

| Return | preLog | postLog | errorLog | |---|---|---|---| | T (sync) | before call | after return | on sync throw | | Promise<T> | before call | on resolve | on reject | | Observable<T> | before call | on each emission | on stream error |

The decorator is intentionally timing-free. For duration / latency / histogram metrics, use @rnw-community/histogram-metric-decorator — the two decorators compose via stacking (@HistogramMetric() @Log(...) method(...)) with no overlap of concerns.

Type narrowing — no factory generics needed

Callback parameter types flow from the decorated method's signature through the factory's <K extends AnyFn, TArgs extends Parameters<K>, TResult extends GetResultType<ReturnType<K>>> generic shape. In simple cases — sync or Promise-returning methods with typed arguments — the callback params narrow automatically. Under experimentalDecorators TypeScript occasionally fails to back-flow the method signature into unannotated callback params (the generic binds at the decoration site, not at the factory call); when you see callback params typed as unknown or any, annotate the callback params directly. Never spell out factory generics.

import { createLogDecorator, consoleTransport } from '@rnw-community/log-decorator';

const Log = createLogDecorator({ transport: consoleTransport });

class OrderService {
    @Log(
        orderId => `placing order ${orderId}`,
        (result, orderId) => `order ${orderId} placed: ${result.id}`,
        (error, orderId) => `order ${orderId} failed: ${String(error)}`
    )
    placeOrder(orderId: string): { id: string } {
        return { id: `ord-${orderId}` };
    }
}

orderId narrows to string, result to { id: string }, error is unknown. Promise<T> and Observable<T> return types unwrap automatically — TResult is the awaited or emitted value.

Omit any hook to skip that lifecycle event. Hook results that are empty strings (static '' or a callback returning '') are skipped too — handy for conditional messages.

Public API

Observable support

Observable returns are handled internally — no opt-in, no strategy wiring. rxjs is an optional peer; install it only when your methods return Observable.

import { createLogDecorator, consoleTransport } from '@rnw-community/log-decorator';

const Log = createLogDecorator({ transport: consoleTransport });

class StreamService {
    @Log(
        symbol => `subscribing to ${symbol}`,
        (tick, symbol) => `${symbol} tick: ${tick}`,
        (error, symbol) => `${symbol} stream errored: ${String(error)}`
    )
    subscribe$(symbol: string): Observable<number> { /* ... */ }
}

License

MIT