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-rel

v0.0.10

Published

Transparent references in JSON

Downloads

18

Readme

json-rel

:link: Transparent references in JSON


json-rel converges the following standards and libraries in order to help normalize JSON reference/relationship descriptors:

  • JsonPath
    • Specification: http://goessner.net/articles/JsonPath/
    • Library: https://www.npmjs.com/package/jsonpath
  • JsonPointer
    • Specification: http://tools.ietf.org/html/draft-ietf-appsawg-json-pointer-08
    • Library: https://www.npmjs.com/package/jsonpointer
  • JsonQuery
    • Library: https://www.npmjs.com/package/json-query

The goal is to increase developer transparency and to provide a unified, semantic interface for working with related JSON data.

Aside from being all around simple, json-rel spares library developers from having to:

  1. decide between which reference specifications(s) to support in your projects
  2. write an interface for when more than one standard needs support
  3. bottleneck integrators of your library into a certain specificaton
  4. write a mechanism that provides a consistent return format (e.g. array vs. element)

Installation

npm install json-rel

Usage

This example shows how to use the main feature of json-rel, which is being able to provide any relationship or reference string to $, an "operator" which will automatically identify the correct specification to use based on the relation itself:

import $ from 'json-rel'

const data = {
  foo: {
    bar: true
  }
}

let query   = $('foo.bar').use(data).get()   // true
let path    = $('$.foo.bar').use(data).get() // true
let pointer = $('/foo/bar').use(data).get()  // true

If you want to be slightly more concise:

let query   = $('foo[bar]', data).get()  // true
let path    = $('$.foo.bar', data).get() // true
let pointer = $('/foo/bar', data).get()  // true

You may also, of course, access and use each specification individually:

import {query, path, pointer} from 'json-rel'

query('foo[bar]', data).get()   // true
path('$.foo.bar', data).get()   // true
pointer('/foo/bar', data).get() // true

You can also infer the specification directly from the relation itself via which:

import which from 'json-rel'

which('foo[bar]')  // -> json-query
which('$.foo.bar') // -> json-path
which('/foo/bar')  // -> json-pointer