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

stringify-body

v1.4.2

Published

Creates test json files suitable for serverless AWS lambda functions.

Downloads

21

Readme

stringify-body

Description

Creates test json files suitable for serverless AWS lambda functions. Files will be created in a directory called "tests".

Usage

  1. In the root of your AWS lambda microservice, create a javascript file to create the templates for your test json files. Each module propery that is exported from this javascript file will be created as its own json file with the tests directory.
// templates.js

module.export = {
  myFile: {
    someData: ["blah", "blah", "blah"],
  },
};
  1. Run stringify-body, passing the path to the file containing your templates with the -p or --path flag. Optionally, you can define a custom output directory name with the -n or --name flag, the default output directory is tests
npx stringify-body -p templates.js

Output:

  1. You can now pass the path to your test json file to a serverless lambda function when invoking locally
sls invoke local --function myFunction --path tests/myFile.json

Nested Directories

For better organization, you may want to nest certain files together in a nested directory. This is acheivable by prefixing the exported module property with a $. Then, each property within that object will generate its own json file nested beneath the parent directory.

// templates.js

module.exports.$nestedDirectory = {
  nestedFile: {
    someData: ["blah", "blah", "blah"] 
  },
  secondNestedFile: {
    someData: ["bing", "bang", "pow"] 
  }
}

Output:

Notes

The directory containing your test json files can also be added to the exclude section of your serverless.yml file to reduce package size.

Using the shorthand -p for --path has issues per: https://github.com/serverless/serverless/issues/7871

Author Info