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

json-templates

v5.1.0

Published

Simple JSON value templating.

Downloads

93,880

Readme

json-template

Simple JSON value templating.

Usage

Here's how you can use this library. Begin by installing via NPM:

npm install json-templates

Here's a small example of usage showing the simplest case, a single string.

const parse = require('json-templates');

const template = parse('{{foo}}');

console.log(template.parameters); // Prints [{ key: "foo" }]

console.log(template({ foo: 'bar' })); // Prints "bar"

Parameters can have default values, specified using a colon. These come into play only when the parameter is undefined.

const template = parse('{{foo:bar}}');

console.log(template.parameters); // Prints [{ key: "foo", defaultValue: "bar" }]

console.log(template()); // Prints "bar", using the default value.

console.log(template({ foo: 'baz' })); // Prints "baz", using the given value.

Parameters can come from a nested object.

const template = parse('{{foo.value:baz}}');

console.log(template.parameters); // Prints [{ key: "foo.value", defaultValue: "baz" }]

console.log(template()); // Prints "baz", using the default value.

console.log(template({ foo: { value: 'bar' } })); // Prints "bar", using the given value.

// Example with parameter coming from array
const template = parse({ a: '{{foo.1:baz}}' });

console.log(template.parameters); // Prints [{ key: "foo.1", defaultValue: "baz" }]

console.log(template()); // Prints { a: "baz" }, using the default value.

console.log(template({ foo: ['baq', 'bar'] })); // Prints { a: "bar" }, using the given value of array.

Context values could be objects and arrays.

const template = parse('{{foo:baz}}');

console.log(template.parameters); // Prints [{ key: "foo", defaultValue: "baz" }]

console.log(template()); // Prints "baz", using the default value.

console.log(template({ foo: { value: 'bar' } })); // Prints { value: 'bar' } , using the given value.

The kind of templating you can see in the above examples gets applied to any string values in complex object structures such as ElasticSearch queries. Here's an example of an ElasticSearch query.

const template = parse({
  index: 'myindex',
  body: {
    query: {
      match: {
        title: '{{myTitle}}',
      },
    },
    facets: {
      tags: {
        terms: {
          field: 'tags',
        },
      },
    },
  },
});

console.log(template.parameters); // Prints [{ key: "myTitle" }]

console.log(template({ title: 'test' }));

The last line prints the following structure:

{
  index: "myindex",
  body: {
    query: {
      match: {
        title: "test"
      }
    },
    facets: {
      tags: {
        terms: {
          field: "tags"
        }
      }
    }
  }
}

The parse function also handles nested arrays and arbitrary leaf values. For more detailed examples, check out the tests.

Why?

The use case for this came about while working with ElasticSearch queries that need to be parameterized. We wanted the ability to specify query templates within JSON, and also make any of the string values parameterizable. The ideas was to make something kind of like Handlebars, but just for the values within the query.

We also needed to know which parameters are required to "fill in" a given query template (in order to check if we have the right context parameters to actually execute the query). Related to this requirement, sometimes certain parameters should have default values. These parameters are not strictly required from the context. If not specified, the default value from the template will be used, otherwise the value from the context will be used.

Here's how the above title parameter could have a default value of test:

{
  "index": "myindex",
  "body": {
    "query": {
      "match": {
        "title": "{{title:test}}"
      }
    },
    "facets": {
      "tags": {
        "terms": {
          "field": "tags"
        }
      }
    }
  }
}

Also it was a fun challenge and a great opportunity to write some heady recursive functional code.

Related Work