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

gp-seattle-inventory-api

v0.0.5

Published

This package contains different APIs that perform operations against the relevant DynamoDB tables.

Downloads

3

Readme

GP Seattle Inventory APIs

This package contains different APIs that perform operations against the relevant DynamoDB tables.

APIs

There are a list of APIs that have been implemented in the api folder. The API classes all contain the following:

  • public constructor(client: DBClient, metrics?: MetricsClient)
    • Public constructor to initialize the API class. Requires a DBClient, which main current implementation is DDBClient. Optionally, accepts a MetricsClient, which main current implementation is CloudWatchClient.
  • public static NAME: string
    • This is the name used to initialize the router transaction
  • public router(number: string, request: string, scratch?: ScratchInterface): string | Promise<string>
    • This is the main function that is used to understand router requests.
  • public execute(scratch: ScratchInterface): Promise<?>
    • This is the main function that is used to execute the specific API. This is the function that should be used to call the API from code.
  • interface ScratchInterface
    • Interface defining the variables that are expected for the execute function. Note that this interface is not exported.

Router

One way the APIs are linked up is through the router, where a user can either use a SMS or CLI (for dev) dialogue to invoke APIs.

The SMS router is invoked through sending a message to the designated number, which triggers a SNS notification, which in turn triggers a Lambda invocation of the SMS router code.

A CLI router was created for the purposes of testing, which can be invoked by pulling the code, then running the following:

  • npm install
  • npm run build
  • From the __dev__/handlers/router directory: node CLIRouter.js