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

jsonsmith

v0.1.17

Published

resolves a series of inputs to a single json value.

Downloads

931

Readme

jsonsmith

resolves a series of inputs to a single json value.

Usage:

cobble(options)

options has the following properties:

  • inputs (required): a list of inputs where each element can be one of the following:

    • a string representing a file path -- jsonsmith will try to figure out the format if not provided explicitly
    • an object with properties path and format, where format can be one of json, yaml, and properties
    • an object with property raw that maps to a value in json, yaml, or .properties format
  • varsObj: an optional object that will be used as the context for interpolation will be done and passed in as the last input

  • debug: (line: string) => void: optional

Interpolation

  • a value with syntax %{VARIABLE_NAME}% will be evaluated in the context of varsObj

File paths

  • $read_text(path: string) will be interpreted as a file containing text.
  • $read_json(path: string) will be interpreted as a file containing json.
  • $read_yaml(path<string>) will be interpreted as a file containing yaml.

Examples

With file paths

import { cobble } from 'jsonsmith'

cobble({
  inputs: [
     'someDir/yaml1.yaml',
     'someDir/yaml2.yaml'
    ]
 });

This will do a deep extends with target being the first argument provided, and subsequent arguments as sources.

With raw inputs

import { cobble } from 'jsonsmith'

cobble({
  inputs: [
    {
      "raw": {
        "version": "0.5",
        "appName": "app"
      }
    },
    {
     "raw": "version=1.0"
    }
  ]
})

The above would result in the following object

{
  "appName": "app",
  "version": "1.0"
}

With interpolation

import { cobble } from 'jsonsmith'

cobble({
  inputs: [
    {
     "raw": "template=$read_json('templates/template.json')"
    },
    {
     "raw": "version=%{APP_VERSION}%"
    }
  ],
  varsObj: { APP_VERSION: "1.7" }
})

where templates/template.json looks like

{
  "name": "Scott Storch",
  "subject": "Mellow my man"
}

would result in the following object

{
  "template": {
    "name": "Scott Storch",
    "subject": "Mellow my man"
  },
  "version": "1.7"
}