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

jsonary

v0.0.16

Published

Jsonary - use JSON Schema in your client

Downloads

31

Readme

Jsonary on Node.js

WARNING: rendering functionality is rather limited at the moment

This package makes the Jsonary library available on Node.js.

What is Jsonary?

Jsonary is a library for dealing with data and APIs that are described by JSON (Hyper-)Schema. It can find and fetch schemas referenced from HTTP headers, allowing you to use the API in a flexible way.

It also contains a rendering system, using schema constraints and hyper-schema links to assemble adaptive clients for your APIs. This is currently only in the browser, but the final steps for getting it working on Node are being worked on.

The goal is that you should be able to write a Jsonary renderer once, and it should generate static HTML on Node, and provide part of a snazzy AJAX client on the browser.

So what can I do with it on Node right now?

Right now, the rendering system doesn't quite work, but you can still other (slightly less cool) schema-aware features of Jsonary.

For example, here is a short script that scrapes a (JSON Hyper-Schema described) API, starring every document written by someone whose name begins with 'J':

var Jsonary = require('jsonary');

var results = [];
Jsonary.getData('http://example.com/documents/', function (documents) {
	documents.items(function (index, docData) {
		var authorLink = docData.getLink('author');
		var starLink = docData.getLink('star');
		if (authorLink && starLink) {
			authorLink.follow(null, false).getData(function (authorData) {
				var authorName = authorData.get('/name');
				if (/^J/.test(authorName)) {
					starLink.follow(null, false);
				}
			});
		}
	});
});

That script knows nothing about any URL apart from the entry-point - the link information is taken from the hyper-schema referenced by the data.

Jsonary also implements a basic cookie store, so your scripts can log in to an API before using it:

var Jsonary = require('jsonary');

Jsonary.getData('http://example.com/json/', function (basePage) {
	var loginLink = basePage.getLink('login');
	loginLink.follow({username: "hello", password: "world"}, false).getData(function (loginResult) {
		assert(loginResult.get('/success') == true);
		performLoggedInActions();
	});
});

loginLink will be followed at whatever URL, and with whatever method and Content-Type is appropriate. For maximum flexibility, the login data should probably have used link.createSubmissionData(), in case there are other required parameters:

var loginLink = basePage.getLink('login');
loginLink.createSubmissionData(function (loginData) {
	loginData.set('/username', "hello");
	loginData.set('/password', "world");
	loginLink.follow(loginData, false).getData(...);
});