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

@linzjs/lambda

v4.1.0

Published

### _A minimal lambda wrapper for LINZ Javascript lambda function development_

Downloads

92

Readme

Lambda wrapper @linzjs/lambda

A minimal lambda wrapper for LINZ Javascript lambda function development

  • Automatically chooses the correct HTTP output event format based on input event (API Gateway, ALB, FunctionURL or Cloudfront)
  • Generates a request id for every request using a ULID
  • Automatically Logs the correlationId if one is provided to the function.
  • Logs a meta log at the end of the request @type: "report"
  • Tracks performance and logs request duration & metrics using @linzjs/metrics

Why?

This repository wraps the default lambda handler so it can be invoked by ALB, API Gateway or Cloudfront without requiring code changes, while also apply a opinionated set of lambda defaults

Http

import { lf, LambdaHttpResponse } from '@linzjs/lambda';

// This works for Cloudfront, FunctionURL, ALB or API Gateway events
export const handler = lf.http();

handler.router.get('/v1/ping', () => new LambdaHttpResponse(200, 'Ok'));
handler.router.get<{ Params: { style: string } }>(
  '/v1/style/:style.json',
  (req) => new LambdaHttpResponse(200, 'Style: ' + req.params.style),
);

// Handle all requests
handler.router.get('*', () => new LambdaHttpResponse(404, 'Not found'));

// create middleware to validate api key on all requests
handler.router.hook('request', (req) => {
  const isApiValid = validateApiKey(req.query.get('api'));
  // Bail early
  if (!isApiValid) return new LambdaHttpResponse(400, 'Invalid api key');

  // Continue
  return;
});

Lambda

import { lf } from '@linzjs/lambda';

export const handler = lf.handler<S3Event>(async (req) => {
  if (req.event.Records.length === 0) throw new Error('No records provided');
  for (const evt of req.event.Records) {
    req.log.info({ key: evt.key }, 'Request s3');
  }
});

Request ID generation

A ULID is generated for every request and can be accessed at req.id

every log message generated by req.log will by include the request id.

Metrics

Simple timing events can be tracked with timer see @linzjs/metrics

req.timer.start('some:event');
// Do Work
const duration = req.timer.end('some:event');

TODO: this should eventually be replaced by open telemetry spans

Metalog

At the end of every request a metalog is logged with use information for monitoring and alerting in something like elasticsearch, to add additional keys to the metatalog use req.set()

req.set('xyz', { x, y, z });
req.set('location', { lat, lon });

Pino logging

Automatically includes a configured pino logger

function doRequest(req) {
  req.log.info('Some Log line'); // Includes useful information like requestId
}

This can be overridden at either the wrapper

export const handler = lf.wrap(doRequest, myOwnLogger);

of set a different default logger

lf.logger = myOwnLogger;
export const handler = lf.wrap(doRequest);