webpack-merge
Variant of merge that's useful for webpack configuration
webpack-merge@6.0.1 was published on 2024-07-02. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=18.0.0.
All webpack-merge versions · Permanent reference to 6.0.1
Package specifications
| Version | 6.0.1 |
|---|---|
| License declaration | MIT |
| Published | 2024-07-02T07:39:22.644Z |
| Node.js requirement | >=18.0.0 |
| Type declarations | Bundled declarations |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 48.34 KiB |
| Published file count | 21 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | dist/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 7 |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install webpack-merge 6.0.1
npm install webpack-merge@6.0.1 pnpm add webpack-merge@6.0.1 yarn add webpack-merge@6.0.1
Runtime dependencies
- flat ^5.0.2
- wildcard ^2.0.1
- clone-deep ^4.0.1
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- clone-deep@4.0.1 — direct
- flat@5.0.2 — direct
- is-plain-object@2.0.4 — indirect
- isobject@3.0.1 — indirect
- kind-of@6.0.3 — indirect
- shallow-clone@3.0.1 — indirect
- wildcard@2.0.1 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
Evidence and freshness
- https://registry.npmjs.org/webpack-merge/6.0.1 — retrieved 2026-10-29T11:31:23.844Z
- https://api.deps.dev/v3/systems/npm/packages/webpack-merge/versions/6.0.1 — retrieved 2026-10-29T11:31:24.393Z
- https://api.deps.dev/v3/systems/npm/packages/webpack-merge/versions/6.0.1:dependencies — retrieved 2026-10-29T11:31:24.413Z