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

@codingitwrong/jsonapi-client

v0.0.11

Published

A vanilla JS client for JSON:API services

Downloads

684

Readme

@codingitwrong/jsonapi-client

A lightweight client for making requests to a JSON:API service.

  • It doesn't attempt to provide a way to utilize every possible feature of JSON:API; instead, it offers a core set of functionality sufficient for most apps.
  • It doesn't attempt to abstract away the JSON:API object format; instead, it returns JSON:API data as-is.

Synopsis

import {ResourceClient} from '@codingitwrong/jsonapi-client';

const resource = new ResourceClient({
  name: 'widgets',
  httpClient: axios.create(...),
});

resource.all()
  .then(response => console.log(response.data));

resource.create({
  attributes: {
    title: 'My Widget',
  },
});

Installation

$ npm install --save @codingitwrong/jsonapi-client

or

$ yarn add @codingitwrong/jsonapi-client

@codingitwrong/jsonapi-client needs to be configured with an httpClient object that handles the requests and responses. The easiest way to do this is to provide an axios instance configured with your server's base URL, the standard JSON:API content type, and optionally any authentication info your server requires.

import axios from 'axios';
import {ResourceClient} from '@codingitwrong/jsonapi-client';

const token = 'FILL_ME';

const httpClient = axios.create({
  baseURL: 'https://jsonapi-sandbox.herokuapp.com',
  headers: {
    'Authentication': `Bearer ${token}`,
  },
});
const client = new ResourceClient({name: 'widgets', httpClient});

client.all().then(results => console.log(results));

Usage

Reading Data

all

To retrieve all of the records for a resource, call the all() method. The method returns a promise that will resolve to the server's JSON response:

resource.all().then(response => console.log(response.data));

find

To retrieve a single record by ID, call the find() method:

resource.find({id: 42}).then(response => console.log(response.data));

where

To filter/query for records based on certain criteria, use the where method, passing it an object of filter keys and values to send to the server:

const filter = {
  category: 'whizbang',
};
resource.where({filter}).then(response => console.log(response.data));

related

Finally, to load records related via JSON:API relationships, use the related method. A nested resource URL is constructed like categories/27/widgets. (In the future we will look into using HATEOAS to let the server tell us the relationship URL).

const parent = {
  type: 'category',
  id: 27,
};

resource.related({parent}).then(response => console.log(response.data));

By default, the name of the relationship on parent is assumed to be the same as the name of the other model: in this case, widgets. In cases where the names are not the same, you can explicitly pass the relationship name:

const parent = {
  type: 'categories',
  id: 27,
};

const relationship = 'purchased-widgets';

resource
  .related({parent, relationship})
  .then(response => console.log(response.data));

Writing

create

Creates a new record. The object passed in should follow the JSON:API object format, but the type can be omitted:

widgetResource.create({
  attributes: {
    'name': 'My Widget',
    'creation-date': '2018-10-07',
  },
});

This isn't just limited to attributes; relationships can be passed in too.

update

Updates a record. Takes the id of the record and the attributes and/or relationships to update. No type argument is required, but if passed in it's ignored, so you can pass in a full record if you like.

widgetResource.update({
  id: '42',
  attributes: {
    name: 'My Updated Widget',
  },
});

This isn't just limited to attributes; relationships can be passed in too.

delete

Deletes the passed-in record. Only the id property is used, so you can pass either a full record or just the ID:

widgetResource.delete({id: 42});

Options

All methods that return records (so, all but delete()) take an optional options property, consisting of an object of additional options to pass. Each key/value pair in the object is translated into a query string parameter key/value pair:

resource.all({
  options: {
    include: 'comments',
  },
});

// requests to widgets?include=comments

License

Apache-2.0