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

call-capture

v0.2.1

Published

Capture calls and property assignments on an object

Downloads

3

Readme

capture

Wrap around an object and capture sets on its properties and calls on its methods.

usage

node

const capture = require("call-capture");

browser

<html>
<head>
    <meta charset="UTF-8">
    <script src="src/capture.js"></script>
</head>
<body>
<script>
// capture is in the global scope
</script>
</body>
</html>

deferring

// assume we have a canvas on a webpage
var ctx = capture(canvas.getContext("2d"));

// call and set on the capture object, will not execute immediately
ctx.beginPath();
ctx.lineWidth = 5;
ctx.moveTo(5, 10);
ctx.lineTo(70, 60);
ctx.stroke();

// examine queued commands
console.log(ctx.queue[1]);

// modify queued command arguments
ctx.queue[1].args[1] += 10;	// now becomes ctx.moveTo(5, 20)

// execute all queued commands
ctx.executeAll();

// execute a specific one in the queue
ctx.queue[3].execute();

// clear queued commands (won't clear automatically after executing)
ctx.clearQueue();

indirect wrapping

If you don't have access to object creation (for example if it's done in a library), then you can patch its creation function.

// wrap around with canvas drawing
var oldGetContext = HTMLCanvasElement.prototype.getContext;
HTMLCanvasElement.prototype.getContext = function () {
    return capture(oldGetContext.apply(this, arguments));
};

It's not recommended to try wrapping the CanvasRenderingContext2D's prototype directly because it contains native calls.

immediate execution

If you don't actually to defer anything, but instead capture them, then that is available via the immediatelyExecute option:

var ctx = capture(canvas.getContext("2d"), {immediatelyExecute: true});

This and other options can be configured by directly modifying the captured object:

ctx.opts.executeImmediately = false;

pause/start capturing

You can suspend capture and execute commands immediately by calling

ctx.pauseCapture();
// immediately executed commands on ctx...
ctx.resumeCapture();