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

store-failed-reports

v1.0.0

Published

Lambda to store failed reports when an error occurs

Downloads

7

Readme

Store failed reports

This lambda takes the following input and executes an API call to subscriptions to store failures. The template.yaml file in this folder is for independent integration testing purposes only.

{ 
  'options': {    
    'subscriptionsHost': 'string',
    'environment': 'string',
    'timeout': int,
  }
}

Build and Test Locally

Build the lambda function using the sam build command.

$ sam build

The SAM CLI installs dependencies defined in ./package.json, creates a deployment package, and saves it in the ./.aws-sam/build folder.

Test a single function by invoking it directly with a test event. An event is a JSON document that represents the input that the function receives from the event source. Test events are included in the ./events sub folder of this lambda.

Run functions locally and invoke them with the sam local invoke command.

$ sam local invoke StoreFailedReportsFunction --event events/event.json

The SAM CLI can also emulate your application's API. Use the sam local start-api to run the API locally on port 3000.

$ sam local start-api

The SAM CLI reads the application template to determine the API's routes and the functions that they invoke. The Events property on each function's definition includes the route and method for each path.

      Events:
        SetWarehouse:
          Type: Api
          Properties:
            Path: /store-failed-reports
            Method: get

Unit Tests

Tests are defined in the ./tests folder in this project. Use NPM to install the Jest test framework and run unit tests.

$ npm install
$ npm test