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 🙏

© 2025 – Pkg Stats / Ryan Hefner

lltrace-aws-sdk

v1.4.3

Published

AWS SDK with methods monkey-patched for tracing - part of lltrace

Downloads

25

Readme

lltrace-aws-sdk


Purpose #######

This is (almost) a drop-in replacement for aws-sdk to be used in AWS Lambda functions.

Some of the methods are monkey-patched to allow for the activity of lambda functions to be traced.

Usage

In your lambda, instead of this:

var aws = require('aws-sdk');

Do this:

var aws = require('lltrace-aws-sdk').AWS;

And then at the top of the handler function:

require('lltrace-aws-sdk').init(context.invokedFunctionArn);

All existing code making use of the aws object should continue working normally.

Requirements ############

  • Create a DynamoDB table with the name lltrace with Primary Key set to:

    1. Partition key Caller of type String

    2. Sort key Target of type String

  • Lambdas using this library need to be able to write to DynamoDB

Under the hood ##############

SNS publish, Lambda invoke and S3 upload operations are traced at the moment.

The appropriate methods are monkey-patched to log the name of the lambda function and what it's doing to DynamoDB (only a subset of all operations are logged, 10% by default).

The entries in DynamoDB can then be used to create the map of the lambdas and how they communicate (SNS, direct invocations etc) and what triggers different lambdas (SNS, S3 events etc).