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

roads-fieldsfilter

v1.3.0

Published

A tool to turn complex API data into optimized JSON responses. Can significantly improve performance.

Downloads

18

Readme

Roads - Fields Filter

A library to help optimize JSON representations, by only executing logic when the associated field is requested by the client.

Roads.FieldsFilter

Many APIs benefit from allowing users to limit which fields they want. If a user is only trying to display title and description, there's no need to provide tons of unrelated stats and metadata. This is the first benefit of the fields filter. When provided the response data of a route, and an array of valid fields, The field filter will remove any unwanted fields.

    var f = new FieldsFilter({
        'test' : {
            'one' : true,
            'two' : true
        },
        'hello' : {
            'one' : true,
            'two' : true
        }
    });

    // notice test.two was not requested, so it's ignored
    // notice hello was requested, so the entire child resource is provided
    f.filter(['test.one', 'hello'])
        .then(function (response) {
            console.log(response === {
                'test' : {
                    'one' : true
                },
                'hello' : {
                    'one' : true,
                    'two' : true
                }
            });
        });

The second benefit is that you can provide function or promise values and the filter will expand them ONLY if the user has explicitly requested them. This allows you to avoid heavy DB queries or cache hits by intelligently structuring your responses.

    var f = new FieldsFilter({
        'test' : {
            'one' : function () {
                return true;
            },
            'two' : function () {
                console.log('this will never be reached!');
                return true;
            }
        },
        'hello' : {
            'one' : true,
            'two' : true
        }
    });

    // notice test.two was not requested, so it's ignored and the function is never executed
    // notice test.one was requested, so the function is executed and the response is provided
    f.filter(['test.one', 'hello'])
        .then(function (response) {
            console.log(response === {
                'test' : {
                    'one' : true
                },
                'hello' : {
                    'one' : true,
                    'two' : true
                }
            });
        });

new FieldsFilter(dynamic data)

Create an object to help filter down a set of data

name | type | description -----------|------------------------------------|--------------- data | dynamic | A piece of data that needs to be expanded and or filtered

    var f = new FieldsFilter({"hello" : "goodbye"});

filter(Array fields)

Filter down a set of data based on a whitelist of fields

name | type | description -----------|------------------------------------|--------------- fields | dynamic | An array of fields that should remain in the response. To represent a heirarchy use periods

Reduce the data associated with this filter object to only contain the fields provided in the "fields" array If true is passed, the whole object will be expanded and all fields returned.

    var f = new FieldsFilter({
        'test' : {
            'one' : true,
            'two' : true
        },
        'hello' : {
            'one' : true,
            'two' : true
        }
    });

    f.filter(['test.one', 'hello'])
        .then(function (response) {
            console.log(response === {
                'test' : {
                    'one' : true
                },
                'hello' : {
                    'one' : true,
                    'two' : true
                }
            });
        });