Repository navigation
Releases
@stackline/deepmerge 1.1.2
Release of @stackline/deepmerge 1.1.2, using the exact npm package published by GitHub Actions.
- npm: https://www.npmjs.com/package/@stackline/deepmerge/v/1.1.2
- Source: 198e0c2
- Publication workflow: https://github.com/alexandroit/stackline-deepmerge/actions/runs/41915538102
- SHA-512:
8c922e9213bca03baa619fcb11c9df0778057a6d7982ffb48f149655669df9cf5b10fda92f94b35363c09502871c62b0d2a75d4c6a5c9609d951a63708cba4c6
The attached tarball matches the original publication artifact and npm registry bytes. Package identity, source commit, publication run and SLSA provenance were verified. Existing npm versions are not republished.
@stackline/deepmerge 1.1.0
Drop-in replacement for deepmerge 4. Without options, results now match deepmerge@4.3.1 exactly: values, own-key order, prototypes, descriptors, and independent copies of repeated references. Every Stackline addition is opt-in.
npm install deepmerge@npm:@stackline/deepmergeFixed
- A repeated input reference could receive another branch's merged result instead of its own copy.
- Keys replaced by the source moved to the end of the result; key order and
JSON.stringifyoutput now match deepmerge 4. - Repeated non-cyclic references were shared in the result; they are now independent copies, as in deepmerge 4.
- React 19 elements are atomic instead of having their props merged (deepmerge#265).
merge.alland the other static helpers are typed on the ESM default export.
Changed
- Defaults follow deepmerge 4: falsy options and hooks fall back to the defaults,
constructorandprototypeare handled like deepmerge 4, andmaxDepthandmaxKeysare unlimited.__proto__is still dropped at every depth, so CVE-2026-93753, which affectsdeepmerge@4.3.1, does not apply. - The 1.0 hardening is available through
strict,unsafeKeys: 'strict', and explicit limits. Configurations that already setonUnsafeKeykeep the 1.0 key policy. - About 2.3 times the 1.0.4 throughput, and about 30% faster than
deepmerge@4.3.1, on the included benchmark.
Added
strict,strictOptions, andcreateDeepmerge(defaults).unsafeKeys,skipUndefined,mergeCollections(MapandSet), andcustomMergeScopeoptions.- A third
customMergeargument with the property path and both values. isPlainMergeableObjectto keep class instances and built-ins intact.- Array strategies:
overwriteArrays,mergeArraysByIndex,concatUniqueArrays, andmergeArraysByKey(selector).
Verification
- An exact differential suite compares complete output graphs with
deepmerge@4.3.1: 900,000 comparisons without a difference. - deepmerge's own 4.3.1 test suite (115 assertions) and README examples pass against this package.
- Every published CVE-2026-93753 attack variant is covered.
- How every upstream issue, pull request, and fork is handled · Compatibility contract · Changelog
Published with npm provenance by workflow run 38433471277.
SHA-512: 6c44351295eb96ef4f4d380a0fdcfce4c5981a30ccbfbf5f176aa7d8b61d9ae929ba3ea89e49f991995102ed0f699bd4bfd6507abc2d0d5808127d8b62db04ef
@stackline/deepmerge 1.0.4
Documentation and package discovery update for @stackline/deepmerge@1.0.4.
Uses the published 1.0.2 tarball as the baseline. Only the README and package version, keywords and homepage changed. All other 23 file contents are identical; runtime/development dependencies, original authors and license are preserved.
Documentation · Publication evidence
SHA-512: c50cdd73783d878e50c3dcf751580d8bcc5b40d30db8a091f4f63392e0654895b227d66d71936dccf5c11bdd988bebeb31063d3d8302c7f107bd624d36561827
@stackline/deepmerge 1.0.3
Historical documentation-only publication, superseded by @stackline/deepmerge@1.0.4. Runtime files and dependency requirements are unchanged from 1.0.2. Original authors and licenses remain preserved.
Original GitHub Actions publication
SHA-512: 7e983b407529dfee78589514e4b0bd7f92c03529292a0d01f59df18de6bf89b7196cf2961ca73facba8fabd076262796193ce07cf36dc8e0d679736a2262a8f0
@stackline/deepmerge 1.0.1
Adoption-focused patch release with executable security and compatibility examples, direct and alias migration guidance, reproducible benchmark documentation, public catalog integration, and digest-gated release automation. Runtime APIs and declarations are unchanged.
@stackline/deepmerge v1.0.0
First public release of a secure, immutable, zero-dependency deep merge implementation.
- Compatible with the documented deepmerge v4 API and npm alias migration
- Filters prototype-pollution keys or rejects them in strict mode
- Preserves cycles and shared references with bounded traversal
- Ships ESM, callable CommonJS, browser global, source maps, and TypeScript 3.9-7.0 declarations
- Validated on Node.js 14.17-24, Linux, macOS, Windows, Deno, and Bun
The attached tarball is byte-identical to the artifact published to Verdaccio and public npm. SHA-1: 192fd05ea69417fda7223c3f2b9bed83b3b96d0a.