extend

npmv3.0.2

Port of jQuery.extend for node.js and the browser

Not recommended for new projects

No — extend should not be adopted for new projects. Last published 2974 days ago.

AAdoption: grade A, Excellent.
68.3M downloads per week and 2 known dependents.
FMaintenance: grade F, Failing.
Last published 2974 days ago.
AWeight: grade A, Excellent.
Zero runtime dependencies, about 23 KB installed.
ASupply chain: grade A, Excellent.
No install scripts, 2 maintainers, and a contained dependency surface.
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 extend to a project.

Direct dependencies

Runtime packages this one declares itself.

Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

23 KB

Install size

Unpacked size of this package plus its entire runtime tree.

—

Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js: No constraint declared
Module format: CommonJS only
TypeScript: No bundled types
Install scripts: None

Quick start

A usage example from the extend README.

jsFull README ↗

var extend = require('extend');
extend(targetObject, object1, object2);

extend 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
extendthis page	68.3M	2	MIT	8 years ago
deepmerge	0	5	MIT	1 day ago
type-fest	337.8M	6	(MIT OR CC0-1.0)	1 day ago
merge-descriptors	113M	1	MIT	1 day ago
@ungap/structured-clone	75.6M	2	ISC	1 day ago
rfdc	46.8M	3	MIT	1 day ago

Dependencies

Declared by extend v3.0.2. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (5)

@ljharb/eslint-config ^12.2.1covert ^1.1.0eslint ^4.19.1jscs ^3.0.7tape ^4.9.1

Used by

Popular packages that depend on extend.

requestnpm

Simplified HTTP request client.

↓ 12.5M/wk◈ 4 dependents⚖ Apache-2.0deprecated

gaxiosnpm

A simple common HTTP client specifically for Google APIs and services.

↓ 0/wk◈ 1 dependents⚖ Apache-2.0TS

Relationship graph

Dependencies (left) and dependents (right) of extend.

extend dependencies dependents

Frequently installed together

undici-typesnpm

A stand-alone types package for Undici

↓ 284M/wk◈ 3 dependents⚖ MITTS

https-proxy-agentnpm

An HTTP(s) proxy `http.Agent` implementation for HTTPS

↓ 225.1M/wk◈ 10 dependents⚖ MIT

node-fetchnpm

A light-weight module that brings Fetch API to node.js

↓ 172.9M/wk◈ 9 dependents⚖ MITTS

expressnpm

Fast, unopinionated, minimalist web framework

↓ 92.8M/wk◈ 17 dependents⚖ MIT

corsnpm

Node.js CORS middleware

↓ 69.7M/wk◈ 6 dependents⚖ MIT

webpacknpm

Packs ECMAScript/CommonJs/AMD modules for the browser. Allows you to split your codebase into multiple bundles, which can be loaded on demand. Supports loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.

↓ 49.8M/wk◈ 29 dependents⚖ MITTS

@types/corsnpm

TypeScript definitions for cors

↓ 0/wk◈ 4 dependents⚖ MITTS

is-dockernpm

Check if the process is running inside a Docker container

↓ 0/wk◈ 2 dependents⚖ MITTS

@types/nodenpm

TypeScript definitions for node

↓ 0/wk◈ 327 dependents⚖ MITTS

uuidnpm

RFC9562 UUIDs

↓ 254.8M/wk◈ 8 dependents⚖ MITTS

mime-typesnpm

The ultimate javascript content-type utility.

↓ 185.3M/wk◈ 9 dependents⚖ MIT

tunnel-agentnpm

HTTP proxy tunneling agent. Formerly part of mikeal/request, now a standalone module.

↓ 36.6M/wk◈ 1 dependents⚖ Apache-2.0

Release history

No releases in the last two years, typically about 206 days apart.

Recent versions of extend
Version	Published	Size	License
2.0.2	8 years ago	24 KB	MIT
3.0.2latest	8 years ago	23 KB	MIT
3.0.1	9 years ago	—	MIT
3.0.0	11 years ago	—	MIT
2.0.1	11 years ago	—	MIT
2.0.0	12 years ago	—	MIT
1.3.0	12 years ago	—	MIT
1.2.1	13 years ago	—	MIT
1.2.0	13 years ago	—	MIT
1.1.3	13 years ago	—	MIT
1.1.1	14 years ago	—	MIT
1.1.0	14 years ago	—	MIT
1.0.0	15 years ago	—	MIT

Overview

extend is an npm package that port of jQuery.extend for node.js and the browser. It is extremely widely used, with about 68.3M downloads per week and 2 known dependents in the graph. The latest version is 3.0.2, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need port of jQuery.extend for node.js and the browser and value a battle-tested, widely-adopted 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

Large, well-established user base (68.3M weekly downloads).
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

justmoon ljharb

Keywords

clone extend merge

Frequently asked questions

Should I use extend?

No — extend should not be adopted for new projects. Last published 2974 days ago.

How do I install extend?

Run `npm install extend` to add extend to your npm project.

What license is extend released under?

extend is distributed under the MIT license.

How popular is extend?

extend has approximately 68,314,937 downloads per week and 2 known dependent packages.

Is extend still maintained?

The most recent release of extend (v3.0.2) was published 8 years ago.

Does extend run install scripts?

No. extend does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.