es/minifier: prototype key lookup treats unknown computed properties as absent

Describe the bug

does_key_exist recursively inspects an object-literal proto value. A computed property whose key is not statically equal to x is treated as a definite nonmatch; the helper returns Some(false) instead of unknown, allowing the inherited read to become undefined.

Input code

function f(k){return ({__proto__:{[k]:42}}).x} console.log(f('x'))

Config

Options used by the exact-source reproduction:

{
  "compress": {},
  "mangle": false,
  "module": false
}

Link to the code that reproduces this issue

Portable input and settings in SWC Playground

SWC Info output

Source build of swc_ecma_minifier 61.0.5, commit 246e6156ca14eaa07243ac8d9aa994c91c95cf3d, macOS arm64, Rust 1.96.0-nightly (f5eca4fcf 2026-04-09), Node v20.20.2.

The observed checkout and freshly fetched authoritative origin/main are the same commit. Fetch: git fetch --no-tags origin main, 2026-09-09T03:15:52Z, repository swc-project/swc. Reproduction was performed in a separate checkout of that fetched commit. Thus the cause remains on the default branch, not only in an older release.

For minify cases, the source harness follows the repository example: parse, resolve bindings, convert Terser compressor options, call optimize, apply fixer, emit, and execute original/output separately. Script-only behavior uses Script parsing. The playground carries portable source/settings; its published version is not evidence that the release matches the pinned source build. No implementation change was applied.

Expected behavior

Exit 0; stdout:

42

Actual behavior

function f(k){}console.log(f("x"));

Exit 0; stdout:

undefined

Version

swc_ecma_minifier 61.0.5, 246e6156ca14eaa07243ac8d9aa994c91c95cf3d (also freshly fetched main).

Additional context

Responsible code: compress/pure/member_expr.rs:190.

Proposed Scope

Return unknown when unresolved computed keys are encountered at any prototype-recursion level. Apply this uncertainty consistently to computed data, method, getter, and setter keys while preserving statically known presence/absence decisions.

Limit the change to this semantic boundary and its regression coverage. No API expansion, dependency update, migration, deployment, or feature-flag rollout is required. Preserve the documented minifier assumptions; the reproduction does not require overriding builtin implementations.

Acceptance Criteria and Test Scenarios

• The primary input must print 42.
• A prototype literal {x:42} must still yield 42.
• Use k="other" and verify x remains undefined.
• Cover an additional nested proto layer and a computed method key without changing observable property lookup.
• Add regression coverage in the existing SWC-owned fixture/execution suites under crates/swc_ecma_minifier/tests/fixture/issues, or the existing tests/eval.rs API harness for the Evaluator case. Check exact execution/return values and valid generated syntax, not only snapshots.
• Initialize submodules, update fixture expectations only as needed, and rerun cargo test -p swc_ecma_minifier without UPDATE. Preserve passing controls above. Keep regression comments in English.

Duplicate search

No same-root open duplicate was found in bounded searches including "computed" "prototype" and related minifier terms. Similar issues were evaluated by root cause and transformation boundary.

Out of Scope

Unrelated rewrites, new user options, implementing other audit findings, and changing semantic assumptions.

This is a message for readers, not the author of this issue.

Please read no +1 before leaving a comment.