deepmerge
npmv4.3.1A library for deep (recursive) merging of Javascript objects
Not recommended for new projects
No — deepmerge should not be adopted for new projects. Last published 1273 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 1273 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 30 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding deepmerge to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- node >=0.10.0
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the deepmerge README.
const x = {
foo: { bar: 3 },
array: [{
does: 'work',
too: [ 1, 2, 3 ]
}]
}
const y = {
foo: { baz: 4 },
quux: 5,
array: [{
does: 'work',
too: [ 4, 5, 6 ]deepmerge vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| deepmergethis page | 0 | 5 | MIT | 3 years ago |
| rfdc | 46.8M | 3 | MIT | 19 hours ago |
| extend | 68.3M | 2 | MIT | 1 day ago |
| defaults | 0 | 1 | MIT | 19 hours ago |
| copy-anything | 0 | 1 | MIT | 15 hours ago |
| type-fest | 337.8M | 6 | (MIT OR CC0-1.0) | 1 day ago |
Dependencies
Declared by deepmerge v4.3.1. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (11)
Used by
Popular packages that depend on deepmerge.
No description provided.
A library for interacting with the app.json
React Native CLI
This package is part of the [React Native CLI](../../README.md). It contains commands for managing the configuration of React Native app.
This package is part of the [React Native CLI](../../README.md). It contains commands for diagnosing and fixing common Node.js, iOS, Android & React Native issues.
Relationship graph
Dependencies (left) and dependents (right) of deepmerge.
Frequently installed together
The semantic version parser used by npm.
the most correct and second fastest glob implementation in JavaScript
TypeScript execution environment and REPL for node.js, with source map support
Transpile JSX, TypeScript and esnext features on the fly with esbuild
A module for reading, writing, and manipulating JSON files
Reusable require and Node resolution utilities library for Expo
Types for the Expo config object app.config.ts
Slugifies a String
Get and typecast environment variables.
A library for Expo config plugins
Resolve the workspace root using bun, npm, pnpm, or yarn
Convert Windows backslash paths to slash paths
Release history
No releases in the last two years, typically about 30 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 4.3.1latest | 3 years ago | 30 KB | MIT |
| 4.3.0 | 3 years ago | 30 KB | MIT |
| 4.2.2 | 6 years ago | 29 KB | MIT |
| 4.2.1 | 6 years ago | 29 KB | MIT |
| 4.2.0 | 6 years ago | 29 KB | MIT |
| 4.1.2 | 6 years ago | 26 KB | MIT |
| 4.1.1 | 7 years ago | 26 KB | MIT |
| 4.1.0 | 7 years ago | 26 KB | MIT |
| 4.0.0 | 7 years ago | 25 KB | MIT |
| 3.3.0 | 7 years ago | 22 KB | MIT |
| 3.2.1 | 7 years ago | 21 KB | MIT |
| 3.2.0 | 7 years ago | 21 KB | MIT |
| 3.1.0 | 7 years ago | 20 KB | MIT |
| 3.0.0 | 7 years ago | 22 KB | MIT |
| 2.2.1 | 8 years ago | 25 KB | MIT |
Overview
deepmerge is an npm package that a library for deep (recursive) merging of Javascript objects. It has 5 known dependents in the graph. The latest version is 4.3.1, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need a library for deep (recursive) merging of Javascript objects and value a focused solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Clear open-source license (MIT).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use deepmerge?
No — deepmerge should not be adopted for new projects. Last published 1273 days ago.
How do I install deepmerge?
Run `npm install deepmerge` to add deepmerge to your npm project.
What license is deepmerge released under?
deepmerge is distributed under the MIT license.
How popular is deepmerge?
npm does not publish download counts. Within PackageGraph's crawl, 5 known packages depend on deepmerge.
Is deepmerge still maintained?
The most recent release of deepmerge (v4.3.1) was published 3 years ago.
Does deepmerge run install scripts?
No. deepmerge does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.