JavaScript Interview Questions
  • JavaScript Interview Questions
  • Contact
  • Introduction
  • Question 1
  • Question 2
  • Question 3
  • Question 4
  • Question 5
  • Question 6
  • Question 7
  • Question 8
  • Question 9
  • Question 10
  • Question 11
  • Question 12
  • Question 13
  • Question 14
  • Question 15
  • Question 16
  • Question 17
  • Question 18
  • Question 19
  • Question 20
  • Question 21
  • Question 22
  • Question 23
  • Question 24
  • Question 25
  • Question 26
  • Question 27
  • Question 28
  • Question 29
  • Question 30
  • Question 31
  • Question 32
  • Question 33
  • Question 34
  • Question 35
  • Question 36
  • Question 37
  • Question 38
  • Question 39
  • Question 40
  • Question 41
  • Question 42
  • Question 43
  • Question 44
  • Question 45
  • Question 46
  • Question 47
  • Question 48
  • Question 49
  • Question 50
  • Question 51
  • Question 52
  • Question 53
  • Question 54
  • Question 55
  • Question 56
  • Question 57
  • Question 58
  • Question 59
  • Question 60
  • Question 61
  • Question 62
  • Question 63
  • Question 64
  • Question 65
  • Question 66
  • Question 67
  • Question 68
  • Question 69
  • Question 70
  • Question 71
  • Question 72
  • Question 73
  • Question 74
  • Question 75
  • Question 76
  • Question 77
  • Question 78
  • Question 79
  • Question 80
  • Question 81
  • Question 82
  • Question 83
  • Question 84
  • Question 85
  • Question 86
  • Question 87
  • Question 88
  • Question 89
  • Question 90
  • Question 91
  • Question 92
  • Question 93
  • Question 94
  • Question 95
  • Question 96
  • Question 97
  • Question 98
  • Question 99
  • Question 100
  • Epilogue
Powered by GitBook
On this page
  • Question
  • Answer

Question 58

Question

Can you explain how to use proxy.revocable property to revoke a proxy object?

Answer

The proxy.revoke() method is crucial for managing Proxy objects effectively, allowing you to break the association between your proxy and the original target object.

Here's how it works:

const handler = { get: value => console.log(`Getting: ${value}`) }; 
const myProxy = new Proxy({ name: 'Alice' }, handler);

// ... use the proxy as usual... 

console.log(myProxy.name); // Outputs "Getting: Alice"

// Revoke the proxy
const {revoke} = myProxy;  
revoke();

// Now, trying to access the proxy will throw an error
console.log(myProxy.name); // Throws TypeError: Cannot read property 'name' of undefined

Explanation:

  1. Creating the Proxy: We define a handler and create a Proxy object targeting an object with the property name.

  2. Using the Proxy: The code demonstrates accessing the name property through the proxy, triggering the get handler to log "Getting: Alice".

  3. Revocation: We access the revoke() function from the proxy itself (it's an internal property). Calling revoke() effectively undoes the association between the proxy and its target object.

  4. Consequences of Revocation:

    • Any subsequent attempts to access properties through the revoked proxy will throw a TypeError. The proxy is no longer valid.

    • The original target object remains unchanged.

Important Points:

  • revoke() acts immediately; it doesn't wait for the next operation on the proxy.

  • Use revocation when you need to release resources associated with the proxy, or when you want to prevent further manipulation of a target object after a certain point in your code.

PreviousQuestion 57NextQuestion 59

Last updated 9 months ago