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

velson

v0.1.4

Published

A simple Node package imitating AWS transformation of JSON using Velocity templates.

Downloads

3

Readme

Velocity-JSON Transformer

npm versionBuild Status

AWS API Gateway currently limits log events to 1 KiB. Log events larger than 1024 bytes, such as request and response bodies,will be truncated by AWS API Gateway before submission to CloudWatch Logs. Thus for large request bodies undergoing template transformation before being forwarded to the http integration backend, debugging a faulty transform becomes guesswork if the error location is within the truncated portion. This tool aims to provide the full transform output by mimicking how AWS API Gateway transforms a JSON-formated request/response body with the Integration Request/Response Method's mapping template.

This provides a Node wrapper around the Velson jar

Features:
  • Indicating error-causing line number within a mapping template if transform fails.
  • Checks for malformed JSON.
  • Checks for duplicate properties within generated JSON.
  • Provides a well formatted JSON output.

*Note: Not all AWS Mapping Template built-in functions and variables are currently supported.

Built-in Functions | Description | Supported | --- | --- |--- | $input.json(x) | Evaluates a JSONPath expression and returns the results as a JSON string. |yes $input.path(x) | Takes a JSONPath expression string (x) and returns an object representation of the result. |yes $util.base64Encode() | Encodes the data into a base64-encoded string. |yes $util.base64Decode() | Decodes the data from a base64-encoded string. |yes

Prerequisite
Usage

Velson provides both a command line interface to allow for local transforms within the terminal and an API for embedding within your programs, whichever is most convenient.

Installation
$ npm install --save velson
var transformer = require("velson")

const templatePath = './template.vm';
const requestFilePath = './request.json';

const engine = new transformer.VelsonEngine();
try {
  engine.initialize(templatePath, requestFilePath);
  const transformedOutput = engine.transform();
  console.log(JSON.stringify(transformedOutput, null, 2));
} catch (error) {
  console.log(error.message);
}
Using Velson CLI
$ npm install -g velson
$ velson

  Usage: velson [options]


  Options:

    -V, --version           output the version number
    -t, --template [value]  Path to the Velocity template mapping file. (required)
    -r, --request [value]   Path to request JSON file. (required)
    -h, --help              output usage information
$ velson -t ./template.vm -r ./request.json

template.vm

#set($source = $input.path('$'))
{
  "source": {
    "integerProperty": $source.integerProperty,
    "numberProperty": $source.numberProperty,
    "nullPropertyInQuotes": "$source.nullProperty",
    "stringProperty": "$source.stringProperty",
    "arrayProperty": $source.arrayProperty,
    "arrayPropertySize": $source.arrayProperty.size(),
    "booleanProperty": $source.booleanProperty,
    "missingProperty": "$source.missingProperty"
  },
  "input-json": {
    "integerPropertyViaJson": $input.json('$.integerProperty'),
    "numberPropertyViaJson": $input.json('$.numberProperty'),
    "nullPropertyViaJson": $input.json('$.nullProperty'),
    "stringPropertyViaJson": $input.json('$.stringProperty'),
    "arrayPropertyViaJson": $input.json('$.arrayProperty'),
    "arrayPropertyTestViaJson": $input.json('$.arrayProperty[0].test'),
    "booleanPropertyViaJson": $input.json('$.booleanProperty'),
    "missingPropertyViaJson": $input.json('$.missingProperty')
  },
  "util": {
    "base64EncodedStringProperty": "$util.base64Encode($source.stringProperty)",
    "originalStringPropertyDecoded": "$util.base64Decode($util.base64Encode($source.stringProperty))"
  }
}

request.json

{
    "integerProperty": 1,
    "numberProperty": 2.6,
    "nullProperty": null,
    "stringProperty": "string",
    "arrayProperty": [
      {
        "itemOne": 1,
        "test": "here"
      },
      {
        "itemOne": 2,
        "test": "there"
      }
    ],
    "booleanProperty": true
}