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

@justin8-cdk/python-lambda

v1.2.8

Published

> TODO: description

Downloads

2

Readme

CDK Python Lambda Function

This module provides a self-building Python Lambda module that generates a layer for the dependent packages from your requirements.txt dynamically. It will automatically compile the libraries using the correct version of python as you have specified. Usage is almost identical to a regular lambda except the asset source/build dir is defined automatically using Code.fromAsset.

Requirements:

  • The source for the Lambda must be in src/${name}, where ${name} is the name used in creation of the CDK construct
  • build/* must be in git ignore.
  • Docker installed and running (it is used to build against the correct Python version)

Usage

new PythonLambda(this, "function1", {
  handler: "index.lambda_handler",
  runtime: lambda.Runtime.PYTHON_3_8,
});

With the following file structure:

root
|-- src
|   |-- index.py <-- Contains a "lambda_handler" function that is called upon execution by Lambda
|   |-- requirements.txt <-- All of your requirements defined here as usual
|-- build <-- This is in gitignore, doesn't have to exist otherwise; Just contains the layer cache for the required packages

From the above:

  • Any packages listed in requirements.txt will be automatically bundled up in to a layer
  • The packages will be installed via the correctly versioned docker container (provided by lambda.Runtime.*.bundlingDockerImage)
  • The layer will be assigned to the Lambda function that is created
  • The output object will be a regular Lambda function
  • There is an additional property of requirementsLayer on the function if you need to interact with it for some reason