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

submerge

v1.1.4

Published

Recursively merge various objects into a single new object, optionally capable of reflecting changes on the merged object

Downloads

64

Readme

npm version Build Status Coverage Status dependencies dev-dependencies Codacy Badge

node-submerge

Recursively merge various objects into a single new object, optionally capable of reflecting changes on the merged object

Install

npm install --save submerge

As of version 1.1.0 Submerge (mostly its dependencies) requires NodeJS 4 or higher. If you are 'stuck' on NodeJS 0.10 - 0.12, you will need to specify the version (the latest is 1.0.9).

$ npm install --save submerge@^1.0.9

Usage

There are three ways of creating merged objects, all of which are based on the 'first come, first serve'-principle, the first key encountered will be on the merged object. There is one exception, nested object, if a key holds an object and it can inherit one or more properties from another object, it will.

submerge(object A, object B, ...)

This creates a merged object which contains all keys/values encountered in all provided objects. The merged object is fully enumarable and mutable, but changes will only affect the merged object itself

submerge.locked(object A, object B, ...)

This creates a merged object which contains all keys/values encountered in all provided objects. The merged object is enumerable but will have [Getter/Setter] at all keys, any change to existing keys will not be honered. New keys, however, cannot (yet) be prevented.

submerge.live(object A, object B, ...)

This creates a merged object which contains all keys/values encountered in all provided objects. The merged object is enumerable but will have [Getter/Setter] at all keys, any change to existing keys will not only be honered but also persisted in the originating object.

Events

When using the submerge.live method, you may want to know which variables are being changed, this can be done using the event mechanism (which is only available for live merges).

change

Live submerged objects have the change event, this was designed to work from the object returned by submerge.live(...).

var submerge = require('submerge'),
    live = submerge.live({a:'this is a'}, {b:'this is b'});

live.on('change', function(key, newValue, oldValue) {
	console.log('live changed key', key, 'new', newValue, 'was', oldValue);
});

live.a = 'still a, but different';

Do note that as the change handler was designed to be used on the object returned by submerge.live the key will actually use the object dot notation for nested keys, e.g. live.my.object.value will have the key 'my.object.value' in the change-event.

License

GPLv2 © Konfirm Open