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

dcp

v0.3.1

Published

[![npm](https://img.shields.io/npm/v/dcp.svg)](https://www.npmjs.com/package/dcp)

Downloads

6,523

Readme

dcp

npm

This module supports making copy / clone deeply and faster.

DEPRECATED

This package has been deprecated and will be removed from the registry in the near future. If you are using it, please fork it!

Benchmark

  • Node.js: v12.7.0
  • benchmark.js: v2.1.0
yarn benchmark

[1] "dcp" 0.0665μs[1.00][1.00]
[2] "JSON" 3.73μs[0.0178][56.1]
[3] "lodash" 3.76μs[0.0177][56.6]

Usage

Runtime parsing

If the reference of the base object is NOT changed, you can use it without defining a key.

const obj = {
  a: 10,
  c: [1, 2],
  d: {}
};

// only first time, it will be parsed
const newObj = dcp.clone(obj);
/*
 * { a: 10,
 *   b: '',
 *   c: [1, 2],
 *   d: { d1: false } }
 */

Runtime parsing with a key

If the reference is changed but the format is the same, you need to use it with a key.

// only first time, it will be parsed
const newObj = dcp.clone('key1', obj);
/*
 * { a: 10,
 *   b: '',
 *   c: [1, 2],
 *   d: { d1: false } }
 */

// get the default values
const newObj2 = dcp.clone('key1');
/*
 * { a: 0,
 *   b: '',
 *   c: [0, 0],
 *   d: { d1: false } }
 */

Pre-defined

It is the fastest way, but the difference is only the first clone.

const structure = {
  a: 1,
  b: 'default',
  c: [undefined, undefined],
  d: { d1: true }
};
const key = 'test';
dcp.define(key, structure);
const newObj = dcp.clone(key, obj);

APIs

define

arguments: (key: any, structure: any) arguments: (structure: any)

If it is called, functions which have the structure will be made.

clone

arguments: (key: any, structure: any) arguments: (structure: any)

The deep clone will be made by defined structure. If the key isn't defined, define will be called and then the deep clone function will be called.