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-schema-request

v0.4.0

Published

Make requests with json-hyper-schema references

Downloads

5

Readme

JsonSchemaRequest

Allows making requests based on json hyper schema endpoints. Currently a work in progress.

Stability:Experimental NPM Version Travis Issues

Commitizen friendly Semantic Release License Maintenance Downloads

Installation:

npm install json-schema-request

Usage:

example.js

import jsonSchemaRequest from 'json-schema-request';

const myPartialBlogPost = {
    id: 42,
    author: "marvin"
};

jsonSchemaRequest({
    schemaUrl: "http://www.example.com/blog-post.json",
    rel: "self",
    context: myPartialBlogPost
})
    .then(result => console.log);

// {
//     id: 42,
//     author: "marvin",
//     title: "Of diodes and doors",
//     body: "...down the left hand side..."
// }

blog-post.json

{
    "id": "http://www.example.com/blog-post.json",
    "type": "object",
    "properties": {
        "id": { "type": "number" },
        "author": { "type": "string" },
        "title": { "type": "string" },
        "body": { "type": "string" }
    },
    "required": [ "title", "author", "id" ],
    "links": [
        {
            "rel": "self",
            "href": "http://www.example.com/api/post/{id}",
            "method": "GET",
            "targetSchema": { "$ref": "#" }
        }
    ]
}

The schema for the json object passed to jsonSchemaRequest is available in schema/inputSchema.json. The options are documented below as well:

| Option | Required | Description | |----|----|----| | schemaUrl | Yes | URL to load the schema from. References inside this schema that point to other files are also loaded, and inlined. | | rel | Yes | Relationship name for link to request. This is defined in your schema. | | context | | Context data to insert into urls (eg 'id' in example above). | | data | | Data to send along with the request (eg the body for 'create' rels). | | headers | | Header object to pass through to the request. (eg { "Content-Type": "application/json" }) | | schemaPrefix | | The URL to prefix on schema IDs if missing. If you prefer to use relative URLs for your schemaUrl, or id or $ref in your schemas, this sets the server and path those relative URLs are attached to. | | serverRoot | | The URL to prefix on hrefs if missing. If you prefer to use relative URLs for your href this sets the server and path those relative URLs are attached to. |