utils-merge
npmv1.0.1merge() utility function
Not recommended for new projects
No — utils-merge should not be adopted for new projects. Last published 3277 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 3277 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies.
- 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 utils-merge 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.4.0
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the utils-merge README.
var a = { foo: 'bar' }
, b = { bar: 'baz' };
merge(a, b);
// => { foo: 'bar', bar: 'baz' }utils-merge 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 |
|---|---|---|---|---|
| utils-mergethis page | 0 | 1 | MIT | 9 years ago |
| type-fest | 337.8M | 6 | (MIT OR CC0-1.0) | 1 day ago |
| lodash | 147.8M | 20 | MIT | 1 day ago |
| mime | 136.4M | 6 | MIT | 1 day ago |
| meow | 36.7M | 1 | MIT | 1 day ago |
| unicorn-magic | 31.6M | 1 | MIT | 1 day ago |
Dependencies
Declared by utils-merge v1.0.1. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (3)
Used by
Popular packages that depend on utils-merge.
Relationship graph
Dependencies (left) and dependents (right) of utils-merge.
Frequently installed together
An AST-based pattern checker for JavaScript.
Node.js final http responder
Lightweight debugging utility for Node.js and the browser
parse a url with memoization
Release history
No releases in the last two years.
| Version | Published | Size | License |
|---|---|---|---|
| 1.0.1latest | 9 years ago | — | MIT |
| 1.0.0 | 13 years ago | — | MIT |
Overview
utils-merge is an npm package that merge() utility function. It has 1 known dependents in the graph. The latest version is 1.0.1, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need merge() utility function 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).
- Lean dependency tree (3 direct dependencies).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Keywords
Frequently asked questions
Should I use utils-merge?
No — utils-merge should not be adopted for new projects. Last published 3277 days ago.
How do I install utils-merge?
Run `npm install utils-merge` to add utils-merge to your npm project.
What license is utils-merge released under?
utils-merge is distributed under the MIT license.
How popular is utils-merge?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on utils-merge.
Is utils-merge still maintained?
The most recent release of utils-merge (v1.0.1) was published 9 years ago.
Does utils-merge run install scripts?
No. utils-merge does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.