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

aws-lambda-utilities

v1.0.13

Published

AWS Lambda Utilities and Helper Functions

Readme

aws-lambda-utilities

Useful utilities and functions for aws lambda projects

Using the logger

The logger class uses Winston logger.

Importing the logger:

import { Logger } from 'aws-lambda-utilities';

Create a new instance of the logger class:

const logger = new Logger();

Log a info message:

logger.info('Received event');

Log a info message with an object:

logger.info('Received event', { event });

Log an error:

logger.error('Lambda error', { error });

Always wrap objects

Using the DefaultVars class

The DefaultVars class exposes a list of standard lambda environment variables.

DefaultVars exposes environment variables through the following methods:

awsProfile(), awsRegion(), nodeEnv(), awsLocalStackEndpoint(), lambdaFunctionName(), lambdaFunctionVersion(), logLevel(), isTest(), isAWS() and isProduction()

Example DefaultVars implementation

Import the class from

import { DefaultVars } from 'aws-lambda-utilities';

Destructure the methods you require:

const { isAWS, lambdaFunctionName, awsLocalStackEndpoint } = new DefaultVars();

Use it in code:

if(!isAWS()) {
  // ...
}

Extending DefaultVars and adding your own methods

Create a new class called EnvVars (recommended naming convention)

import { DefaultVars } from 'aws-lambda-utilities';

const { env } = process;

export class EnvVars extends DefaultVars {
  constructor() {
    super();
  }

  yourEnvVar(): string | undefined {
    return env.YOUR_ENV_VAR;
  }
}

Using the EnvVars class

Then, you can simply reference the EnvVars class instead of the DefaultVars class in your microservice, as the EnvVars class will have all the properties of DefaultVars and EnvVars.

Example usage:

import { EnvVars } from 'envVars';

const { yourEnvVar, isAWS } = new EnvVars();