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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@contrast/patcher

v1.15.0

Published

Advanced monkey patching--registers hooks to run in and around functions

Downloads

72,435

Readme

@contrast/patcher

Monkey patching.

Notes on v5 Parity

This was ported directly from the node-agent but code with every dependency commented out. As a result there are differences in parity.

  1. Removed dependency on AsyncStorage.

    Old Behavior

    Pre and post hooks only run when async storage context indicates an active request scope.

    New Behavior

    Hooks always run, independent of request scope.

  2. Removed dependency on agent and perf-logger.

    Old Behavior

    A configuration setting would allow for logging of perf data of hooks and original function calls.

    New Behavior

    Performance logging of hooks is non-funcitonal.

  3. Removed the dependency on scopes.

    Old Behavior

    One could specify a scope in the hook options and the original function would be run in that scope. This allowed control over when to run instrumentaion based on current scope value.

    Also, the alwaysRun option forced hooks to run independent of scope state.

    New Behavior

    There are no notions of scopes yet in v5. Patcher instrumentation always runs.

    The scope and alwaysRun options are effectively ignored.

  4. Removed the dependency on tracker.

    Old Behavior

    We used to short-circuit __add function if tracker showed all arguments to be untracked.

    New Behavior

    We do not make this check; no short-circuiting.