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

@beardedtim/config-mapper

v0.1.2

Published

A basic object to object mapper

Downloads

11

Readme

Config Mapper

One final schema to bind them

Usage

yarn add @beardedtim/config-mapper

Mapper

Mapper : Object -> Object -> Object
const Mapper = (config, input) => Object

The config object must look like the following:

const config = {
  [FINAL_KEY_NAME_DESIRED]: {
    resourceName: [KEY_NAME_ON_INPUT_DATA],
    {...otherValues}
  }
}
  • Each key on the config object is the key that we desire on the output object.
  • Each key MUST have a resourceName and that is to be set to the key on the input object that we want to map to the config key.
  • We can pass in any other values that this configured object needs.

The input object can be any object with any keys. The following is an example of using this function:

const config = {
  realName: {
    resourceName: 'name'
  },
  username: {
    resourceName: 'handle'
  }
}

const input = {
  handle: 'beardedtim',
  name: 'Tim',
  age: 28
}

const configured = Mapped(config, input)

configured === ({
    realName: {
      value: 'Tim'
    },
    username: {
      value: 'beardedtim'
    },
    age: 28
})

Maker

Maker : Object -> Object -> Object
const Maker = (config, input) => Object

The config object should look like this:

{
  [KEY_WE_WANT_TO_AFFECT]: [FUNCTION_TO_MODIFY_VALUE_AS_NEEDED]
}

The function called will be passed the following values:

  • input[key] : The value of the input object at the given key.
  • key : The key we are currently dealing with.
  • input : The input object we were given this value from.

The input object should look like this:

{
  [KEY_WE_WANT_TO_AFFECT]: [VALUE_WE_WANT_TO_MODIFY]
}

The following is an example of using the Maker function. Suppose that we have data coming into a function that we want to make sure is valid ( we could try/catch our Maker calls and ensure validation or we can truncate text if it is too long coming in as a prop ) for the component/routine/class/et al we are using the input from.

const config = {
  donorIDs: list => list.slice(0,5)
}

const input = {
  donorIDs: [1,2,3,4,5,6,7,8,9,10]
}

const configured = Maker(config,input)

const configured === ({
    donorIDs: [1,2,3,4,5]
})