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

dotty-map

v1.1.1

Published

Rename indexes on JavaScript objects, e.g. to normalize an API response into your internal format.

Downloads

8

Readme

dotty-map

Dotty-map copies properties from a source object to a destination object, optionally renaming them. Dotty-map uses dotty to parse strings like "pie.filling.temperature" into deep property references, on either the source or the destination.

This can be especially useful to normalize an API response into your internal format.

Examples

dottymap = require('dotty-map');
var source = {
  "apples" : 1,
  "bananas" : 2
};
var destination = {};

//Re-key in Spanish
dottymap(source, destination, {
  "apples" : "manzanas",
  "bananas" : "platanos"
});

//destination = {"manzanas":1, "plantanos":2}

By default, dotty-map will ignore keys that are missing on the source.

dottymap(
  {"apples":1, "carrots":3},
  {},
  {"apples":"manzanas", "bananas":"platanos" }
);
//returns {"manzanas":1} because the source doesn't have bananas, and the map doesn't have carrots.


dottymap(
  {"apples":1, "carrots":3},
  {"manzanas":42, "plantanos":2},
  {"apples":"manzanas", "bananas":"platanos" }
);
//returns {"manzanas":1, "plantanos":2} because the source doesn't have bananas, but the destination already did.

You can set the fourth argument to true to delete properties on the destination if they are missing on the source:

dottymap(
  {"apples":1},
  {"manzanas":42, "plantanos":2},
  {"apples":"manzanas", "bananas":"platanos" },
  true
);
//returns {"manzanas":1}, the destination had its manzanas overwritten, and its plantanos deleted because the source had no bananas.