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

walter-whitelist

v2.0.0

Published

Whitelist javascript objects

Downloads

43

Readme

walter-whitelist Build Status codecov

This lightweight module whitelists javascript objects recursively. This is particularly useful in the following situations:

  • you have to check that a user-supplied object only contains keys that the user is allowed to supply, e.g., when handling a POST/PUT request
  • you have to pick fields from an object that the user is allowed to see, e.g., before sending a response to a client

Walter Whitelist

Examples

Process user-supplied objects

Before storing user-supplied data in a database, you usually want to check if the object contains fields that the user is allowed to store.

let allowed = {name: true, age: true};
whitelist({name: 'Darth', age: 42}, allowed); // resolves with {name: 'Darth', age: 42}
whitelist({id: 23}, allowed); // rejects with WhitelistError (field 'id' is not allowed)
whitelist({name: 'Darth'}, allowed); // resolves with {name: 'Darth', age: undefined}
// omit keys with undefined values:
whitelist({name: 'Darth'}, allowed, {omitUndefined: true}); // resolves with {name: 'Darth'}

You can also use a function to check fields:

let allowed = {
  name: true,
  age: (age, options) => {
    if (age < 50) return age;
    throw WhitelistError('age must be less than 50', options.path);
  },
};
whitelist({name: 'Darth', age: 42}, allowed); // resolves with {name: 'Darth', age: 42}
whitelist({name: 'Darth', age: 66}, allowed); // rejects with WhitelistError ('age must be less than 50')

Nested objects work, too:

allowed = {name: true, lightsaber: {color: true}};
whitelist({name: 'Darth', lightsaber: {color: 'red'}}, allowed);  // resolves with {name: 'Darth', lightsaber: {color: 'red'}}
whitelist({name: 'Darth'}, allowed);  // resolves with {name: 'Darth', lightsaber: {color: undefined}}
// omit keys with undefined values:
whitelist({name: 'Darth'}, allowed, {omitUndefined: true}); // resolves with {name: 'Darth', lightsaber: {}}

Pick allowed fields

Before sending data from a database to a client, you want to pick only fields that the client is allowed to see. This can be achieved by using the option omitDisallowed: true.

let allowed = {name: true, age: true};
whitelist({id: 23, name: 'Darth', age: 42}, allowed, {omitDisallowed: true}); // resolves with {name: 'Darth', age: 42}
whitelist({id: 23, name: 'Darth'}, allowed, {omitDisallowed: true}); // resolves with {name: 'Darth', age: undefined}
// omitDisallowed can be combined with omitUndefined:
whitelist({id: 23, name: 'Darth'}, allowed,
  {omitDisallowed: true, omitUndefined: true}); // resolves with {name: 'Darth'}

Installation

npm install walter-whitelist

Documentation

const whitelist = require('walter-whitelist');

whitelist(src, allowed, options)

  • src: source object, array or primitive
  • allowed: the checks on src are performed according to this value. The following values are accepted:
    • an object {key: value, ...}:
      • expects src to be an object.
      • iterates over keys and uses the value for whitelisting the corresponding key/value pair in src
      • value can be any value that is accepted as the allowed parameter
    • an array with one element [value]:
      • expects src to be an array
      • iterates over elements of array src and whitelists according to value
      • value can be any value that is accepted as the allowed parameter
    • a function fn(src, options):
      • should return the whitelisted src (directly or via a promise)
      • if omitDisallowed is false and src contains disallowed data, the function is responsible for throwing a WhitelistError (or rejecting the returned promise with a WhitelistError)
    • a boolean: if the value is true, src is allowed and returned as the result
  • options: an object with the following optional keys:
    • omitUndefined: if set to true, it omits fields in the result whose values are undefined
    • omitDisallowed: if set to true, it omits fields from src that are not present in allowed.
    • data: custom data that is recursively passed to any function in the allowed parameter.

The function returns a new object with the whitelisted fields and throws a whitelist.WhitelistError if a field in src is not allowed (unless omitDisallow is true).