Revocable proxies

Problem

What becomes confusing, fragile, or impossible without understanding revocable proxies? This lesson answers that through explanation, a worked example, two runnable exercises, and a reference solution. No teacher-supplied worksheet is required.

JavaScript began as a small browser scripting language, then accumulated object, functional, metaprogramming, module, and runtime capabilities while preserving early coercion rules.

Concept explanation

Revocable proxies belongs to “Metaprogramming without magic”. revocable proxies is inspected by introducing one realistic failure and proving root cause before repair.

For revocable proxies, trace concrete input, state transition, output, and failure through a JavaScript semantic rule observable through values, property operations, scope, calls, or protocol steps.

Execution evaluates expressions against lexical environments. Objects are property tables linked through prototypes; functions are callable objects with closures. Apply that model to supplied normal, boundary, and failure cases; each case below names its input and expected evidence.

Example bank

Compare normal, boundary, failure, and cross-layer cases. Predict each observation before revealing the explanation.

Worked example

Start from supplied lab.mjs. Focus: Capture healthy revocable proxies baseline from: Proxy get/set/ownKeys while delegating through Reflect and recording operations.

1. Run: node lab.mjs
2. Save baseline evidence. Use property descriptors, scope panels, call stacks, console probes, and deliberately tiny cases.
3. Boundary case: Record revocable proxies behavior at: Use symbol key and revocable proxy.
4. Failure case: Diagnose this exact revocable proxies failure before editing: Violate non-configurable ownKeys invariant and capture TypeError.

RESULT
Evidence identifies first divergence, repair changes only proven cause, and rerun restores: Operation log matches access sequence; revocation and invariant enforcement are proven. Starter-level baseline: Two labeled records print in stable order; each exposes value, runtime type, and string representation.

Starter material

Create lab.mjs, paste this exact content, then run the command below.

const cases = [
  { label: "baseline", input: 0 },
  { label: "boundary", input: 1 },
];

function observe(value) {
  // Change only this function while investigating revocable proxies.
  return { value, type: typeof value, text: String(value) };
}

for (const test of cases) console.log(test.label, observe(test.input));

STOP / CLEANUPScripts exit by themselves; no cleanup command required.

Independent exercise

Prove root cause: revocable proxies

1. Create second case from blank file: Record revocable proxies behavior at: Use symbol key and revocable proxy.
2. Then create controlled failure: Diagnose this exact revocable proxies failure before editing: Violate non-configurable ownKeys invariant and capture TypeError.
3. Use Chromium Sources · console · hx · Node REPL to prove behavior, then repair controlled failure.
4. Compare result against supplied acceptance checks and reference approach before marking complete.

Expected result

• Evidence identifies first divergence, repair changes only proven cause, and rerun restores: Operation log matches access sequence; revocation and invariant enforcement are proven.
• Two labeled records print in stable order; each exposes value, runtime type, and string representation.
• Controlled revocable proxies failure produces captured evidence; repair restores stated invariant without hiding error.

Hints

Solution

Attempt both exercises before opening reference approach.