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

@fast-ninjas/cdk-constructs

v1.5.8

Published

This repository contains high level AWS CDK constructs. These are designed for my personal and organizational use cases.

Downloads

87

Readme

Welcome to Cloudo

This repository contains high level AWS CDK constructs. These are designed for my personal and organizational use cases.

You may use it in your own projects if it fits your needs. Please do so at your own risk!

I do not guarantee these are good for your own use, bug free or safe to use.

Top Level Constructs

To create a any app, we would create one of these

  • API: A web API
  • StaticSite: A web site created from html css etc
  • Job: Some background job triggered by an event or a time schedule

APP -> CloudoApp -> Api | StaticSite | Job | - Bucket - Authentication -

import { ILayerVersion } from "aws-cdk-lib/aws-lambda";

type PythonFunctionV2Props = { path: string; description?: string; environment?: { [key: string]: string }; layers?: ILayerVersion[]; };

/**

  • Creates a new AWS Lambda function using python runtime.

  • @param path The path to the python function in the format "path/to/functionRootFolder".

  • When using poetry to manage dependencies path must be "path/to/functionRootFolder[.poetry]", the function root folder is the folder containing the pyproject.toml file.

  • The handler function must be in a file named "handler.py" in the package folder.

  • @param dependencyManager The dependency manager to use. Defaults to "poetry". */ export class PythonFunctionV2 extends Construct { constructor(scope: Construct, id: string, props: PythonFunctionV2Props) { super(scope, id);

    const { path, description, environment, layers } = props;
    
    let handlerFileName = "handler.py";
    let handlerFunctionName = "handler";
    let functionRootFolder = path;
    
    if (path.includes(".poetry")) {
      // Poetry project has a package folder with all lower case letters named the same as the project name
      const projectName = path.split(".").splice(-1)[0];
      handlerFileName = `${projectName.toLocaleLowerCase()}/handler.py`;
    }
    const f = new PythonLambdaFunction(this, "Function", {
      functionRootFolder: functionRootFolder,
      handlerFileName,
      handler: handlerFunctionName,
      description,
      environment,
      layers,
    });

    } }