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

jsone

v0.0.0

Published

a format to reference a node within a json object

Downloads

8

Readme

jsone

a format to reference a node within a json object

data

The data encoded into jsone is a sequence of keys.

improper jsone

Improper jsone is a superset of proper jsone.

The keys are given using dot notation or square bracket notation. A key in dot notation must be a valid JavaScript identifier. The key in bracket notation may be an integer or a string.

Dot notation is as follows:

key | dot notation --------------- | ---------------------------------------------------------- "hello" | .hello "helloWorld" | .helloWorld "hello_world" | .hello_world "hello-world" | Not a JavaScript identifier. Use bracket notation instead. 1 | Not a JavaScript identifier. Use bracket notation instead.

If a dot notation key appears first, the dot must be omitted.

Examples:

jsone | parsed --------------- | ---------------------------------------------------------- name | ["name"] location.city | ["location", "city"] .name | Invalid. The dot must be omitted from the first key.

In bracket notation, the name of the key is quoted, unless it's an integer, in which case it can be unquoted. The integers are returned by parse() as numbers. Examples:

jsone | parsed ---------------------------- | ---------------------------------------------------------- [1] | [1] ['Your name'] | ["Your name"] ['employees'][0]['name'] | ["employees", 0, "name"] ["http://example.com/"][0] | ["http://example.com/", 0]

Both dot notation and bracket notation can be combined. Examples:

jsone | parsed ----------------------------------------- | ---------------------------------------------------------- [0].name | [0, "name"] employees[0].name | ["employees", 0, "name"] urls['http://www.google.com/'].visits | ["employees", 0, "name"]

proper jsone

Improper jsone is perfectly fine as input, and it should be treated as such. However, for output, and where unambiguity is needed, proper jsone should be used.

In proper jsone:

  • a key that is a valid identifier must be given using dot notation.
  • an integer identifier must not include quotes
  • a non-integer identifier must be quoted using single quotes

LICENSE

MIT.