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 🙏

© 2025 – Pkg Stats / Ryan Hefner

serialison

v1.2.0

Published

Resolve every link of a {json:api} document

Downloads

21

Readme

SerialiSON

Resolve every link of a {json:api} document

Usage

Install SerialiSON and its dependencies:

npm install serialison

If you want to use SerialiSON in a browser, compile it with npm run build and link your HTML document to one the *.js files in the client directory.

Require the constructor, instanciate it with your document and call the resolve() method:

// The SerialiSON variable is already declared in a browser environment
var SerialiSON = require('serialison');

var myDocument = {
    "posts": {
        "id": "1",
        "title": "Rails is Omakase",
        "links": {
            "author": {
                "id": "9",
                "type": "people"
            },
            "comments": ["1", "2", "3"]
        }
    },
    "linked": {
        "people": [{
            "id": "9",
            "name": "@d2h"
        }],
        "comments": [{
            "id": "1",
            "body": "Mmmmmakase"
        }, {
            "id": "2",
            "body": "I prefer unagi"
        }, {
            "id": "3",
            "body": "What's Omakase?"
        }]
    }
};

var resolver = new SerialiSON(myDocument);

var resolvedDocument = resolver.resolve();

The resolvedDocument variable will contain the following structure:

{
    "posts": {
        "id": "1",
        "title": "Rails is Omakase",
        "author": {
            "id": "9",
            "name": "@d2h"
        },
        "comments": [{
            "id": "1",
            "body": "Mmmmmakase"
        }, {
            "id": "2",
            "body": "I prefer unagi"
        }, {
            "id": "3",
            "body": "What's Omakase?"
        }]
    }
}

Options

You can pass options to the constructor:

new SerialiSON(myDocument, {
    // Options
});

The available options with their default values (syntax based on JSDoc):

{
    /**
     * Set to `false` to disable errors when the documents contain two resources
     * with the same type and ID, the latest resource will override the other ones.
     * @type {Boolean}
     */
    throwErrorsForDuplicateIDs: true,

    /**
     * Set to `false` to disable errors when the documents contain two URL templates
     * with the same path, the latest URL template will override the other ones.
     * @type {Boolean}
     */
    throwErrorsForDuplicateUrlTemplates: true,

    /**
     * Defines the maximum of nested resources the `resolve()` method will process.
     * Raising this value may increase the resolving time, as memory usage.
     * @type {Number}
     */
    maxNestingDepth: 4,

    /**
     * Lists the top level properties except the primary resource. Allows the
     * constructor to find the name of your primary resource. Normally you shouldn't
     * have to use this option but, if your document isn't {json:api} compliant and
     * contains other top level properties, you can add them to this array.
     * @type {string[]}
     */
    topLevelProperties: ['meta', 'links', 'linked'],

    /**
     * Strips the `links` and `linked` top level properties once the document is
     * resolved.
     * @type {Boolean}
     */
    stripTopLinkingProperties: true,

    /**
     * Strips the `links` property from each resource.
     * @type {Boolean}
     */
    stripLinksProperty: true,


    /**
     * A custom transformer to alter an object
     * @callback transformer
     * @param {Object} object - The object to transform
     * @returns {Object} The transformed object
     */

    /**
     * A collection of transformers to execute once the main document has been
     * resolved. Each transformer will receive the main document as the first
     * parameter.
     * @type {transformer[]}
     */
    mainDocumentTransformers: [],

    /**
     * A collection of transformers to execute for each resource once it has been
     * resolved. Each transformer will receive a resource as the first parameter.
     * @type {transformer[]}
     */
    resourceTransformers: []
}

Testing

To run the tests, use the following command:

npm test