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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@ranchonyx/mjson

v1.0.8

Published

A simple system to resolve JSON-references at runtime.

Downloads

14

Readme

mJSON - Modular JSON

Brief

mJSON resolves @import(...)-statements in JSON plaintext or files.
In essence, mJSON allows splitting of large JSON files into several smaller ones which are "assembled" at runtime.

Features

  • Runtime resolution of @import(...)-statements
  • Resolution of local path imports and URL imports
  • Asynchronous and synchronous APIs
    • Note: URL imports are only available in the asynchronous API, the synchronous API will throw.
  • Cyclic import detection
    • Note: When a cyclic import is detected, the API will throw.

Note

When an imported file is being "parsed", it will be treated as mJSON automatically, meaning if it has any @import(...)-statements, they will be resolved.
This results in a practically "infinite" import depth.

Basic usage example (local file import)

The @import(...)-statement in below JSON will be resolved to the parsed JSON contents of the imported file.
Before resolution:

{
  "integer": 1,
  "float": 3.1415,
  "string": "hello there",
  "object": "@import(dist/test/importable-object.mjson)"
}

Executing the resolver:

import {Async} from "@ranchonyx/mjson"

const filePath = "./aboveFile.mjson"
const resolved = await Async.parseFile(filePath);

console.log(resolved);

After resolution:

{
  "integer": 1,
  "float": 3.1415,
  "string": "hello there",
  "object": {
    "name": "Jane Doe",
    "age": 29
  }
}

Side note

If you wish to import a JSON config from a URL / online resource, simply import the URL using @import(https://something.somedomain.com/config).
The resulting text content will be parsed as JSON and then interpreted as mJSON.

Testing

The tests are written using mocha and chai.
Install the devDependencies and run npm test to test the package.

Addendum

I do not see much of any practical purpose for this package, honestly.
I wrote it because I wanted to see if I can write something like this.
If it's any use to you, I'd be glad to hear that.