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

jsonapi-ts-deserializer

v2.3.0

Published

JSON:API deserializer in Typescript

Downloads

13

Readme

JSON:API deserializer in Typescript

cov

A JSON:API response payload is a normalized set of entities and their relationships plus some metadata. This package deserializes a JSON:API response payload into an object graph, using user-defined entity deserializers to build the actual entities.

Installation

npm i jsonapi-ts-deserializer

Usage

import { getDeserializer, ItemDeserializer, RelationshipDeserializer } from 'jsonapi-ts-deserializer';

// Introduce types for your entities, the folder:
type Folder = {
    id: number;
    name: string;
    children: (Folder | File)[];
}

// and the file:
type File = {
    id: number;
    name: string;
}

// Create a deserializer for the folder:
const folderDeserializer : ItemDeserializer<Folder> = {
    type: 'folders',
    deserialize: (item: Item, relationshipDeserializer: RelationshipDeserializer): Folder => {
        const folder: Folder = {
            id: parseInt(item.id),
            name: item.attributes.name,
            children: [],
        };

        folder.children = relationshipDeserializer.deserializeRelationships(relationshipDeserializer, item, 'children');

        return folder;
    },
}

// ...and also for the file:
const fileDeserializer: ItemDeserializer<File> = {
    type: 'files',
    deserialize: (item: Item, relationshipDeserializer: RelationshipDeserializer): File => {
        return {
            id: parseInt(item.id),
            name: item.attributes.name,
        };
    }
}

// create the deserializer with the folder and file deserializers registered:
const deserializer = getDeserializer([
    folderDeserializer,
    fileDeserializer,
]);

// Fetch your JSON:API data:
const yourJsonData = fetch('https://api.example.com/api/folders');

// consume it and get the root items with the complete object-graph:
const rootItems: any[] = deserializer.consume(yourJsonData).getRootItems();

Please note that the deserializer only supports successful responses, and you will get an error if the response is not compatible with the JSON:API specification. I practise the response should be checked for errors before deserializing it and the error handling should be done separately.

Examples

TODO

At least the following things are in the backlog:

  • [X] Ditch the classes in the entity deserializers and use types instead
  • [ ] Consider caching the deserialized entities and reusing them
  • [ ] Come up with a spectacular logo for this package

Credits

Setting up the npm-package with all the bells and whistles would've taken me hours, so I followed the following tutorial for that part:

https://itnext.io/step-by-step-building-and-publishing-an-npm-typescript-package-44fe7164964c