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

unmarshaller

v1.2.2

Published

Toolbox for configuration

Downloads

19

Readme

Unmarshaller

Greenkeeper badge

Toolbox for configuration

Build Status

Motivations

  • A declarative way for defining configuration
  • Reusability and composability
  • Flexible and generic

Installation

npm install --save unmarshaller

Example

import {builder, unmarshal} from 'unmarshaller';

const unmarshaller = {
  editor: builder.string('EDITOR'),
  browser: builder.string('BROWSER'),
};

const lookupFn = (key) => process.env[key];
const config = unmarshal(lookupFn, unmarshaller);

console.log(config);

Basics

Lookup function

You need to provide to the unmarshal function a way to lookup from keys in configuration.

The example above returns the value found in the process's environment:

const lookupFn = (key) => process.env[key];

Unmarshaller

Just an object which represents your configuration.

Builder

Helper functions to build the unmarshaller object.

Default types

| type | |---------| | string | | boolean | | number | | object | | holder | | or |

Default options

|name|type|description| |----|----|-----------| |defaultValue|string|fallback value if the lookup returned undefined or null| |of|array|provide an enumeration of possible values| fallbacks to defaultValue and null.| |parser|function|provide an custom parser function (usually when you want your own types)|

Or

const unmarshaller = {
  foo: builder.or(
    builder.string('foo_a'),
    builder.string('foo_b'),
  )
};

The unmarshalling process will call the lookup function until a value (not undefined or null) is returned.

Extending an existing holder

import {extend, builder} from 'unmarshaller';

const holder = builder.holder({
  editor: builder.string('EDITOR'),
  browser: builder.string('BROWSER'),
});

const extendedHolder = extend(holder, {
  version: builder.string('VERSION'),
});

Extending the default builder

The builder is a regular JavaScript object.

Customizing the builder gives you the possiblity to use your own data converters.

The following example use a custom type: color (which in my use case parses a string into a structure).

import {builder as defaultBuilder} from 'unmarshaller';

export const builder = {
  ...defaultBuilder,
  color: (name, options) => ({
    name,
    parser: parseColor,
    type: 'color',
    ...options
  }),
};

You need to provide a custom parser function (parseColor in the example above). The definition is: function(value: string): string.