fix: use safe property assignment in deepMergeSimple#16271
Merged
Conversation
…gesimple-prototype-safety
…gesimple-prototype-safety
Contributor
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖
Largest pathsThese visualization shows top 20 largest paths in the bundle.Meta file: packages/next/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_shared.json, Out file: esbuild/exports/shared.js
Meta file: packages/richtext-lexical/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_shared.json, Out file: esbuild/exports/shared_optimized/index.js
DetailsNext to the size is how much the size has increased or decreased compared with the base branch of this PR.
|
AlessioGr
requested changes
Apr 13, 2026
AlessioGr
left a comment
Member
There was a problem hiding this comment.
Could you benchmark the new version, the old version, and also try a simple
if (key === '__proto__' || key === 'constructor' || key === 'prototype') {
continue
}check and benchmark if that's faster than Object.defineProperty?
AlessioGr
reviewed
Apr 13, 2026
Contributor
Author
|
AlessioGr
approved these changes
Apr 13, 2026
Contributor
|
🚀 This is included in version v3.83.0 |
milamer
pushed a commit
to milamer/payload
that referenced
this pull request
Apr 20, 2026
# Overview `deepMergeSimple` was not guarding against certain special keys that can trigger inherited setters, causing unexpected behavior on the returned object. Fixed by skipping those keys. ## Key Changes Added an early `continue` for `__proto__`, `constructor`, and `prototype` in both copies of `deepMergeSimple` (`packages/translations` and `packages/ui`) ## Design Decisions Benchmarked this against `Object.defineProperty`, blocklist adds negligible overhead, `Object.defineProperty` was ~5-9x slower. Blocklist is also the standard approach used by lodash and others.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
deepMergeSimplewas not guarding against certain special keys that can trigger inherited setters, causing unexpected behavior on the returned object. Fixed by skipping those keys.Key Changes
Added an early
continuefor__proto__,constructor, andprototypein both copies ofdeepMergeSimple(packages/translationsandpackages/ui)Design Decisions
Benchmarked this against
Object.defineProperty, blocklist adds negligible overhead,Object.definePropertywas ~5-9x slower. Blocklist is also the standard approach used by lodash and others.