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

single-merge

v1.1.1

Published

----- Reasons for choosing single merge ----- 1. single-xxx series plugin each plugin does only one thing 2. the plugin size is less than 1k 3. Provides a merge policy for multiple objects 4. High configuration policy

Downloads

2

Readme

single-merge

description

----- Reasons for choosing single merge -----

  1. single-xxx series plugin each plugin does only one thing
  2. the plugin size is less than 1k
  3. Provides a merge policy for multiple objects
  4. High configuration policy

options

  1. If the first parameter is an array, the second parameter is considered to be config options,The purpose is to merge the elements in the array
    1. 如果第一个参数是数组,那么我们认为的第二个参数一定是config options
  2. if the all parameter is object, there is no need to set parameters {arrayCover}
    1. 如果所有的参数都是对象,我们会忽略arrayCover参数
  3. params[arrayCover]
    1. Under certain requirements, we need to merge arrays instead of overwriting them
    2. arrayCover => true array cover
    3. arrayCover => false array concat
    4. arrayCover default value is true

example for

example1:
const merge = require('single-merge')
const a = {name: 'test', age: 20, arr: [1, 2]}
const b = {name: 'test1', age2: 30, arr: [3, 4]}
const c = {age2: 40, {school: {name: '111'}}}
const result = merge([a, b, c], {arrayCover: false})
=>
{
   name: 'test1',
   age: 20,
   age2: 30,
   arr: [1, 2, 3, 4],
   school: {
      name: '111'
   }
}

example2:
const result = merge(a, b, c)
=>
{
   name: 'test1',
   age: 20,
   age2: 30,
   arr: [3, 4],
   school: {
      name: '111'
   }
}

install

npm install single-merge --save
yarn add single-merge --save

contact me

GitHub