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

beedi

v0.0.6

Published

Make Api's using aws lambda and DI

Downloads

10

Readme

BeeDI / 🐝 DI

BeeDI is an opinionated and lightweight library of helpers for building lambdas. It helps you build tidy and testable lambda functions. It simplifies interfacing with aws event sources by limiting and preparsing the input. The aim is to support all the most common event sources.

Simple Example

import { jsonapi } from 'beedi';

async function main(event) {
  // The handler just contains the logic.
  // event.body has been json parsed.
  return {
    message: 'I get json stringified'
  }
}

export const handler = jsonapi(main);

Why choose BeeDI

Its super early days. BeeDI is not used in production anywhere and is just a fun hobby project. I would not recomend using this in production. If you want something with a similar style but more feature complete, better tested, and well maintained check out https://middy.js.org/ and https://laconiajs.io/.

With that disclamer out the way beedi does have some upsides.

  • It's really lightweight.
  • It has no external dependencies.
  • The interface is really simple. Each helper takes an object that contains just a couple of parameters.
  • No legacy bagage. No support for callbacks. This means less work to maintain it and it is much lighter. This also could be considered a bad thing.
  • The internal code is very low abstraction and very simple. Take a peek under the hood. There really is very little magic to make this happen.

If you give it a try let me know by leaving a star

Table of Contents

Installation

Requirements

Options

Testing

Contributions