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

@x1.co/lambda

v3.6.0

Published

Code to build and deploy for Lambda + API Gateway

Downloads

3

Readme

@x1.co/lambda

Library to build and deploy Next.js apps for AWS Lambda + API Gateway

⚠️ This library is currently in developer preview, and may have limited functionality, bugs, and is not fully tested. The interface may also change in the near future. Use at your own risk.

This library uses the platform-agnostic handlers provided by @x1.co/core and wraps them with a Lambda/API Gateway-compatible layer so that Next.js apps can be served through API Gateway via a HTTP API.

For usage docs, please refer to (TBA).

Architecture

Once built and packaged, the app consists of the following components:

  • default-lambda: handles all requests, including pages, APIs, and regeneration requests.
  • image-lambda: handles image optimization requests.
  • assets: all static assets used by your app.

Infrastructure

You will need the following infrastructure to deploy your app:

  • AWS Lambda
  • AWS API Gateway
  • AWS S3 Bucket
  • AWS SQS Queue (if you are using ISR)
  • AWS CloudFront in front of your API Gateway endpoint, to help with caching, since the APIGateway infra is a HTTP API and can only be regional.
  • additional roles, permissions, etc.

Deployment

We want to empower you to own your own infrastructure code so as to give you the most flexibility for your requirements, so we provide a reference zero-config deployer, which you can easily override resource configurations:

  • (WIP) CDK for Terraform deployer. We have created a reference deployer that allows you to deploy with minimal configuration, and allows you to easily override any resource configuration (e.g S3 bucket names, Lambda memory/timeouts, etc.). Deployments are managed by Terraform, and you can manage deployment state locally or via a number of backends (Terraform, AWS S3, etc.)

Alternatively, you can use this as a standalone builder and bring your own deployment logic.

Limitations

  • Lambda limitations apply: https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html.
  • API Gateway limitations apply: https://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html.
  • The image handler only serves image optimization requests. It cannot redirect, rewrite or add headers (yet).
  • The default and image handlers are separate, so you cannot rewrite from default routes -> image routes. This is by design since generally image optimization requests are only called by the Next.js image component, and also to improve performance so that image optimization code is not included in the default handler/lambda.

Acknowledgments

Special thanks for Jan Varho for the initial prototype which this code is based on.