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

self-referenced-json

v0.0.4

Published

load the json file that is self referenced

Downloads

9

Readme

node-self-referenced-json

Build Status

Load self referenced json to object

  • use $() to add a value reference
  • use &() to add a real object reference
  • use {{}} (mustache style) to add a reference as part of a string

Example

myTemplate.json

{
    "resources": {
        "const_int": 500,
        "some_title_string": "My APP",
        "size": {
            "height": 600, "width": 800
        }
    },
    "window": {
        "help_window": {
            "size": "$(resources.size)",
            "title": "$(resources.some_title_string)"
        }
    },
    "texts": {
        "warning": "windows size should be {{ resources['size'].width }}x{{ resources.size.height }}"
    }
}

myApp.js

var SRJson = require('self-referenced-json');

var mySettings = SRJson.render(require('fs').readFileSync('myTemplate.json', 'utf-8'));
console.log(mySettings.texts['warning']);

Option

var SRJSON = require('self-referenced-json');
SRJson.render('some template here', {

    /*  
     * renderTimes {integer} default:1, times to render.
     *
     *     because the render order is from top to bottom,
     *     if there is a referenced reference which is not rendered yet, 
     *     try to put this value to something larger that 1
     */
    renderTimes: 10,

    /*
     * outputType {String} default:'object'
     *
     *    'object': return a JsonObject
     *    'string': return the serialized string of the object
     *              TAKE CARE!!! circular referenced object cannot be serialized.
     */
    outputType: 'object',

    /*
     * outputType {Object} default: the deserialized template itself
     *
     *    if you want to use other object as the view model, put it here
     */
    renderObj: someOtherObject
});

Option can be undefined, all default values will be used.

Syntax

"$()"

{
    "propA": { "propInsideA": 20 },
    "propB": "$(propA.propInsideA)"
}

returns

{
    propA: { propInsideA: 20 },
    propB: 20
}

"&()"

{
    "propA": { "propInsideA": 20 },
    "propB": "&(propA)"
}

returns

{
    propA: { propInsideA: 20 },
    propB: { propInsideA: 20 }  // if you change the propB.propInsideA, propA.propInsideA will also be changed.
}

take care while using &() with a circular reference, the result could be unexpected.

"{{}}"

same as mustache

{
    "propA": 20,
    "propB": "the value is {{propA}}"
}

returns

{
    propA: 20,
    propB: "the value is 20"
}

Details

please check the source file tests.js for more details.