get, set)get, set)get)set)enumerate trap?Proxies enable you to intercept and customize operations performed on objects (such as getting properties). They are a metaprogramming feature.
In the following example, proxy is the object whose operations we are intercepting and handler is the object that handles the interceptions. In this case, we are only intercepting a single operation, get (getting properties).
const target = {};
const handler = {
get(target, propKey, receiver) {
console.log('get ' + propKey);
return 123;
}
};
const proxy = new Proxy(target, handler);
When we get the property proxy.foo, the handler intercepts that operation:
Consult the reference for the complete API for a list of operations that can be intercepted.
Before we can get into what proxies are and why they are useful, we first need to understand what metaprogramming is.
In programming, there are levels:
Base and meta level can be different languages. In the following meta program, the metaprogramming language is JavaScript and the base programming language is Java.
const str = 'Hello' + '!'.repeat(3);
console.log('System.out.println("'+str+'")');
Metaprogramming can take different forms. In the previous example, we have printed Java code to the console. Let’s use JavaScript as both metaprogramming language and base programming language. The classic example for this is the eval() function, which lets you evaluate/compile JavaScript code on the fly. There are not that many actual use cases for eval(). In the interaction below, we use it to evaluate the expression 5 + 2.
Other JavaScript operations may not look like metaprogramming, but actually are, if you look closer:
// Base level
const obj = {
hello() {
console.log('Hello!');
}
};
// Meta level
for (const key of Object.keys(obj)) {
console.log(key);
}
The program is examining its own structure while running. This doesn’t look like metaprogramming, because the separation between programming constructs and data structures is fuzzy in JavaScript. All of the Object.* methods can be considered metaprogramming functionality.
Reflective metaprogramming means that a program processes itself. Kiczales et al. [2] distinguish three kinds of reflective metaprogramming:
Let’s look at examples.
Example: introspection. Object.keys() performs introspection (see previous example).
Example: self-modification. The following function moveProperty moves a property from a source to a target. It performs self-modification via the bracket operator for property access, the assignment operator and the delete operator. (In production code, you’d probably use property descriptors for this task.)
function moveProperty(source, propertyName, target) {
target[propertyName] = source[propertyName];
delete source[propertyName];
}
Using moveProperty():
> const obj1 = { prop: 'abc' };
> const obj2 = {};
> moveProperty(obj1, 'prop', obj2);
> obj1
{}
> obj2
{ prop: 'abc' }
ECMAScript 5 doesn’t support intercession; proxies were created to fill that gap.
ECMAScript 6 proxies bring intercession to JavaScript. They work as follows. There are many operations that you can perform on an object obj. For example:
prop of an object obj (obj.prop)obj has a property prop ('prop' in obj)Proxies are special objects that allow you customize some of these operations. A proxy is created with two parameters:
handler: For each operation, there is a corresponding handler method that – if present – performs that operation. Such a method intercepts the operation (on its way to the target) and is called a trap (a term borrowed from the domain of operating systems).target: If the handler doesn’t intercept an operation then it is performed on the target. That is, it acts as a fallback for the handler. In a way, the proxy wraps the target.In the following example, the handler intercepts the operations get and has.
const target = {};
const handler = {
/** Intercepts: getting properties */
get(target, propKey, receiver) {
console.log(`GET ${propKey}`);
return 123;
},
/** Intercepts: checking whether properties exist */
has(target, propKey) {
console.log(`HAS ${propKey}`);
return true;
}
};
const proxy = new Proxy(target, handler);
When we get property foo, the handler intercepts that operation:
Similarly, the in operator triggers has:
The handler doesn’t implement the trap set (setting properties). Therefore, setting proxy.bar is forwarded to target and leads to target.bar being set.
If the target is a function, two additional operations can be intercepted:
apply: Making a function call, triggered via
proxy(···)proxy.call(···)proxy.apply(···)construct: Making a constructor call, triggered via
new proxy(···)The reason for only enabling these traps for function targets is simple: You wouldn’t be able to forward the operations apply and construct, otherwise.
If you want to intercept method calls via a proxy, there is one challenge: you can intercept the operation get (getting property values) and you can intercept the operation apply (calling a function), but there is no single operation for method calls that you could intercept. That’s because method calls are viewed as two separate operations: First a get to retrieve a function, then an apply to call that function.
Therefore, you must intercept get and return a function that intercepts the function call. The following code demonstrates how that is done.
function traceMethodCalls(obj) {
const handler = {
get(target, propKey, receiver) {
const origMethod = target[propKey];
return function (...args) {
const result = origMethod.apply(this, args);
console.log(propKey + JSON.stringify(args)
+ ' -> ' + JSON.stringify(result));
return result;
};
}
};
return new Proxy(obj, handler);
}
I’m not using a Proxy for the latter task, I’m simply wrapping the original method with a function.
Let’s use the following object to try out traceMethodCalls():
const obj = {
multiply(x, y) {
return x * y;
},
squared(x) {
return this.multiply(x, x);
},
};
tracedObj is a traced version of obj. The first line after each method call is the output of console.log(), the second line is the result of the method call.
The nice thing is that even the call this.multiply() that is made inside obj.squared() is traced. That’s because this keeps referring to the proxy.
This is not the most efficient solution. One could, for example, cache methods. Furthermore, Proxies themselves have an impact on performance.
ECMAScript 6 lets you create proxies that can be revoked (switched off):
const {proxy, revoke} = Proxy.revocable(target, handler);
On the left hand side of the assignment operator (=), we are using destructuring to access the properties proxy and revoke of the object returned by Proxy.revocable().
After you call the function revoke for the first time, any operation you apply to proxy causes a TypeError. Subsequent calls of revoke have no further effect.
const target = {}; // Start with an empty object
const handler = {}; // Don’t intercept anything
const {proxy, revoke} = Proxy.revocable(target, handler);
proxy.foo = 123;
console.log(proxy.foo); // 123
revoke();
console.log(proxy.foo); // TypeError: Revoked
A proxy proto can become the prototype of an object obj. Some operations that begin in obj may continue in proto. One such operation is get.
const proto = new Proxy({}, {
get(target, propertyKey, receiver) {
console.log('GET '+propertyKey);
return target[propertyKey];
}
});
const obj = Object.create(proto);
obj.bla;
// Output:
// GET bla
The property bla can’t be found in obj, which is why the search continues in proto and the trap get is triggered there. There are more operations that affect prototypes; they are listed at the end of this chapter.
Operations whose traps the handler doesn’t implement are automatically forwarded to the target. Sometimes there is some task you want to perform in addition to forwarding the operation. For example, a handler that intercepts all operations and logs them, but doesn’t prevent them from reaching the target:
const handler = {
deleteProperty(target, propKey) {
console.log('DELETE ' + propKey);
return delete target[propKey];
},
has(target, propKey) {
console.log('HAS ' + propKey);
return propKey in target;
},
// Other traps: similar
}
For each trap, we first log the name of the operation and then forward it by performing it manually. ECMAScript 6 has the module-like object Reflect that helps with forwarding: for each trap
handler.trap(target, arg_1, ···, arg_n)
Reflect has a method
Reflect.trap(target, arg_1, ···, arg_n)
If we use Reflect, the previous example looks as follows.
const handler = {
deleteProperty(target, propKey) {
console.log('DELETE ' + propKey);
return Reflect.deleteProperty(target, propKey);
},
has(target, propKey) {
console.log('HAS ' + propKey);
return Reflect.has(target, propKey);
},
// Other traps: similar
}
Now what each of the traps does is so similar that we can implement the handler via a proxy:
const handler = new Proxy({}, {
get(target, trapName, receiver) {
// Return the handler method named trapName
return function (...args) {
// Don’t log args[0]
console.log(trapName.toUpperCase()+' '+args.slice(1));
// Forward the operation
return Reflect[trapName](...args);
}
}
});
For each trap, the proxy asks for a handler method via the get operation and we give it one. That is, all of the handler methods can be implemented via the single meta method get. It was one of the goals for the proxy API to make this kind of virtualization simple.
Let’s use this proxy-based handler:
> const target = {};
> const proxy = new Proxy(target, handler);
> proxy.foo = 123;
SET foo,123,[object Object]
> proxy.foo
GET foo,[object Object]
123
The following interaction confirms that the set operation was correctly forwarded to the target:
A proxy object can be seen as intercepting operations performed on its target object – the proxy wraps the target. The proxy’s handler object is like an observer or listener for the proxy. It specifies which operations should be intercepted by implementing corresponding methods (get for reading a property, etc.). If the handler method for an operation is missing then that operation is not intercepted. It is simply forwarded to the target.
Therefore, if the handler is the empty object, the proxy should transparently wrap the target. Alas, that doesn’t always work.
this
Before we dig deeper, let’s quickly review how wrapping a target affects this:
const target = {
foo() {
return {
thisIsTarget: this === target,
thisIsProxy: this === proxy,
};
}
};
const handler = {};
const proxy = new Proxy(target, handler);
If you call target.foo() directly, this points to target:
If you invoke that method via the proxy, this points to proxy:
That’s done so that the proxy continues to be in the loop if, e.g., the target invokes methods on this.
Normally, proxies with an empty handler wrap targets transparently: you don’t notice that they are there and they don’t change the behavior of the targets.
If, however, a target associates information with this via a mechanism that is not controlled by proxies, you have a problem: things fail, because different information is associated depending on whether the target is wrapped or not.
For example, the following class Person stores private information in the WeakMap _name (more information on this technique is given in the chapter on classes):
const _name = new WeakMap();
class Person {
constructor(name) {
_name.set(this, name);
}
get name() {
return _name.get(this);
}
}
Instances of Person can’t be wrapped transparently:
jane.name is different from the wrapped proxy.name. The following implementation does not have this problem:
class Person2 {
constructor(name) {
this._name = name;
}
get name() {
return this._name;
}
}
const jane = new Person2('Jane');
console.log(jane.name); // Jane
const proxy = new Proxy(jane, {});
console.log(proxy.name); // Jane
Instances of most built-in constructors also have a mechanism that is not intercepted by proxies. They therefore can’t be wrapped transparently, either. I’ll demonstrate the problem for an instance of Date:
const target = new Date();
const handler = {};
const proxy = new Proxy(target, handler);
proxy.getDate();
// TypeError: this is not a Date object.
The mechanism that is unaffected by proxies is called internal slots. These slots are property-like storage associated with instances. The specification handles these slots as if they were properties with names in square brackets. For example, the following method is internal and can be invoked on all objects O:
O.[[GetPrototypeOf]]()
However, access to internal slots does not happen via normal “get” and “set” operations. If getDate() is invoked via a proxy, it can’t find the internal slot it needs on this and complains via a TypeError.
For Date methods, the language specification states:
Unless explicitly stated otherwise, the methods of the Number prototype object defined below are not generic and the
thisvalue passed to them must be either a Number value or an object that has a[[NumberData]]internal slot that has been initialized to a Number value.
In contrast to other built-ins, Arrays can be wrapped transparently:
The reason for Arrays being wrappable is that, even though property access is customized to make length work, Array methods don’t rely on internal slots – they are generic.
As a work-around, you can change how the handler forwards method calls and selectively set this to the target and not the proxy:
const handler = {
get(target, propKey, receiver) {
if (propKey === 'getDate') {
return target.getDate.bind(target);
}
return Reflect.get(target, propKey, receiver);
},
};
const proxy = new Proxy(new Date('2020-12-24'), handler);
proxy.getDate(); // 24
The drawback of this approach is that none of the operations that the method performs on this go through the proxy.
Acknowlegement: Thanks to Allen Wirfs-Brock for pointing out the pitfall explained in this section.
This section demonstrates what proxies can be used for. That will give you the opportunity to see the API in action.
get, set) Let’s assume we have a function tracePropAccess(obj, propKeys) that logs whenever a property of obj, whose key is in the Array propKeys, is set or got. In the following code, we apply that function to an instance of the class Point:
class Point {
constructor(x, y) {
this.x = x;
this.y = y;
}
toString() {
return `Point(${this.x}, ${this.y})`;
}
}
// Trace accesses to properties `x` and `y`
const p = new Point(5, 7);
p = tracePropAccess(p, ['x', 'y']);
Getting and setting properties of the traced object p has the following effects:
Intriguingly, tracing also works whenever Point accesses the properties, because this now refers to the traced object, not to an instance of Point.
In ECMAScript 5, you’d implement tracePropAccess() as follows. We replace each property with a getter and a setter that traces accesses. The setters and getters use an extra object, propData, to store the data of the properties. Note that we are destructively changing the original implementation, which means that we are metaprogramming.
function tracePropAccess(obj, propKeys) {
// Store the property data here
const propData = Object.create(null);
// Replace each property with a getter and a setter
propKeys.forEach(function (propKey) {
propData[propKey] = obj[propKey];
Object.defineProperty(obj, propKey, {
get: function () {
console.log('GET '+propKey);
return propData[propKey];
},
set: function (value) {
console.log('SET '+propKey+'='+value);
propData[propKey] = value;
},
});
});
return obj;
}
In ECMAScript 6, we can use a simpler, proxy-based solution. We intercept property getting and setting and don’t have to change the implementation.
function tracePropAccess(obj, propKeys) {
const propKeySet = new Set(propKeys);
return new Proxy(obj, {
get(target, propKey, receiver) {
if (propKeySet.has(propKey)) {
console.log('GET '+propKey);
}
return Reflect.get(target, propKey, receiver);
},
set(target, propKey, value, receiver) {
if (propKeySet.has(propKey)) {
console.log('SET '+propKey+'='+value);
}
return Reflect.set(target, propKey, value, receiver);
},
});
}
get, set) When it comes to accessing properties, JavaScript is very forgiving. For example, if you try to read a property and misspell its name, you don’t get an exception, you get the result undefined. You can use proxies to get an exception in such a case. This works as follows. We make the proxy a prototype of an object.
If a property isn’t found in the object, the get trap of the proxy is triggered. If the property doesn’t even exist in the prototype chain after the proxy, it really is missing and we throw an exception. Otherwise, we return the value of the inherited property. We do so by forwarding the get operation to the target (the prototype of the target is also the prototype of the proxy).
const PropertyChecker = new Proxy({}, {
get(target, propKey, receiver) {
if (!(propKey in target)) {
throw new ReferenceError('Unknown property: '+propKey);
}
return Reflect.get(target, propKey, receiver);
}
});
Let’s use PropertyChecker for an object that we create:
> const obj = { __proto__: PropertyChecker, foo: 123 };
> obj.foo // own
123
> obj.fo
ReferenceError: Unknown property: fo
> obj.toString() // inherited
'[object Object]'
If we turn PropertyChecker into a constructor, we can use it for ECMAScript 6 classes via extends:
function PropertyChecker() { }
PropertyChecker.prototype = new Proxy(···);
class Point extends PropertyChecker {
constructor(x, y) {
super();
this.x = x;
this.y = y;
}
}
const p = new Point(5, 7);
console.log(p.x); // 5
console.log(p.z); // ReferenceError
If you are worried about accidentally creating properties, you have two options: You can either wrap a proxy around objects that traps set. Or you can make an object obj non-extensible via Object.preventExtensions(obj), which means that JavaScript doesn’t let you add new (own) properties to obj.
get) Some Array methods let you refer to the last element via -1, to the second-to-last element via -2, etc. For example:
Alas, that doesn’t work when accessing elements via the bracket operator ([]). We can, however, use proxies to add that capability. The following function createArray() creates Arrays that support negative indices. It does so by wrapping proxies around Array instances. The proxies intercept the get operation that is triggered by the bracket operator.
function createArray(...elements) {
const handler = {
get(target, propKey, receiver) {
// Sloppy way of checking for negative indices
const index = Number(propKey);
if (index < 0) {
propKey = String(target.length + index);
}
return Reflect.get(target, propKey, receiver);
}
};
// Wrap a proxy around an Array
const target = [];
target.push(...elements);
return new Proxy(target, handler);
}
const arr = createArray('a', 'b', 'c');
console.log(arr[-1]); // c
Acknowledgement: The idea for this example comes from a blog post by hemanth.hm.
set) Data binding is about syncing data between objects. One popular use case are widgets based on the MVC (Model View Controler) pattern: With data binding, the view (the widget) stays up-to-date if you change the model (the data visualized by the widget).
To implement data binding, you have to observe and react to changes made to an object. In the following code snippet, I sketch how observing changes could work for an Array.
function createObservedArray(callback) {
const array = [];
return new Proxy(array, {
set(target, propertyKey, value, receiver) {
callback(propertyKey, value);
return Reflect.set(target, propertyKey, value, receiver);
}
});
}
const observedArray = createObservedArray(
(key, value) => console.log(`${key}=${value}`));
observedArray.push('a');
Output:
A proxy can be used to create an object on which arbitrary methods can be invoked. In the following example, the function createWebService creates one such object, service. Invoking a method on service retrieves the contents of the web service resource with the same name. Retrieval is handled via an ECMAScript 6 Promise.
const service = createWebService('http://example.com/data');
// Read JSON data in http://example.com/data/employees
service.employees().then(json => {
const employees = JSON.parse(json);
···
});
The following code is a quick and dirty implementation of createWebService in ECMAScript 5. Because we don’t have proxies, we need to know beforehand what methods will be invoked on service. The parameter propKeys provides us with that information, it holds an Array with method names.
function createWebService(baseUrl, propKeys) {
const service = {};
propKeys.forEach(function (propKey) {
service[propKey] = function () {
return httpGet(baseUrl+'/'+propKey);
};
});
return service;
}
The ECMAScript 6 implementation of createWebService can use proxies and is simpler:
function createWebService(baseUrl) {
return new Proxy({}, {
get(target, propKey, receiver) {
// Return the method to be called
return () => httpGet(baseUrl+'/'+propKey);
}
});
}
Both implementations use the following function to make HTTP GET requests (how it works is explained in the chapter on Promises.
function httpGet(url) {
return new Promise(
(resolve, reject) => {
const request = new XMLHttpRequest();
Object.assign(request, {
onload() {
if (this.status === 200) {
// Success
resolve(this.response);
} else {
// Something went wrong (404 etc.)
reject(new Error(this.statusText));
}
},
onerror() {
reject(new Error(
'XMLHttpRequest Error: '+this.statusText));
}
});
request.open('GET', url);
request.send();
});
}
Revocable references work as follows: A client is not allowed to access an important resource (an object) directly, only via a reference (an intermediate object, a wrapper around the resource). Normally, every operation applied to the reference is forwarded to the resource. After the client is done, the resource is protected by revoking the reference, by switching it off. Henceforth, applying operations to the reference throws exceptions and nothing is forwarded, anymore.
In the following example, we create a revocable reference for a resource. We then read one of the resource’s properties via the reference. That works, because the reference grants us access. Next, we revoke the reference. Now the reference doesn’t let us read the property, anymore.
const resource = { x: 11, y: 8 };
const {reference, revoke} = createRevocableReference(resource);
// Access granted
console.log(reference.x); // 11
revoke();
// Access denied
console.log(reference.x); // TypeError: Revoked
Proxies are ideally suited for implementing revocable references, because they can intercept and forward operations. This is a simple proxy-based implementation of createRevocableReference:
function createRevocableReference(target) {
let enabled = true;
return {
reference: new Proxy(target, {
get(target, propKey, receiver) {
if (!enabled) {
throw new TypeError('Revoked');
}
return Reflect.get(target, propKey, receiver);
},
has(target, propKey) {
if (!enabled) {
throw new TypeError('Revoked');
}
return Reflect.has(target, propKey);
},
···
}),
revoke() {
enabled = false;
},
};
}
The code can be simplified via the proxy-as-handler technique from the previous section. This time, the handler basically is the Reflect object. Thus, the get trap normally returns the appropriate Reflect method. If the reference has been revoked, a TypeError is thrown, instead.
function createRevocableReference(target) {
let enabled = true;
const handler = new Proxy({}, {
get(dummyTarget, trapName, receiver) {
if (!enabled) {
throw new TypeError('Revoked');
}
return Reflect[trapName];
}
});
return {
reference: new Proxy(target, handler),
revoke() {
enabled = false;
},
};
}
However, you don’t have to implement revocable references yourself, because ECMAScript 6 lets you create proxies that can be revoked. This time, the revoking happens in the proxy, not in the handler. All the handler has to do is forward every operation to the target. As we have seen that happens automatically if the handler doesn’t implement any traps.
function createRevocableReference(target) {
const handler = {}; // forward everything
const { proxy, revoke } = Proxy.revocable(target, handler);
return { reference: proxy, revoke };
}
Membranes build on the idea of revocable references: Environments that are designed to run untrusted code, wrap a membrane around that code to isolate it and keep the rest of the system safe. Objects pass the membrane in two directions:
In both cases, revocable references are wrapped around the objects. Objects returned by wrapped functions or methods are also wrapped. Additionally, if a wrapped wet object is passed back into a membrane, it is unwrapped.
Once the untrusted code is done, all of the revocable references are revoked. As a result, none of its code on the outside can be executed anymore and outside objects that it has cease to work, as well. The Caja Compiler is “a tool for making third party HTML, CSS and JavaScript safe to embed in your website”. It uses membranes to achieve this task.
The browser Document Object Model (DOM) is usually implemented as a mix of JavaScript and C++. Implementing it in pure JavaScript is useful for:
Alas, the standard DOM can do things that are not easy to replicate in JavaScript. For example, most DOM collections are live views on the current state of the DOM that change dynamically whenever the DOM changes. As a result, pure JavaScript implementations of the DOM are not very efficient. One of the reasons for adding proxies to JavaScript was to help write more efficient DOM implementations.
There are more use cases for proxies. For example:
In this section, we go deeper into how proxies work and why they work that way.
Firefox has allowed you to do some interceptive metaprogramming for a while: If you define a method whose name is __noSuchMethod__, it is notified whenever a method is called that doesn’t exist. The following is an example of using __noSuchMethod__.
const obj = {
__noSuchMethod__: function (name, args) {
console.log(name+': '+args);
}
};
// Neither of the following two methods exist,
// but we can make it look like they do
obj.foo(1); // Output: foo: 1
obj.bar(1, 2); // Output: bar: 1,2
Thus, __noSuchMethod__ works similarly to a proxy trap. In contrast to proxies, the trap is an own or inherited method of the object whose operations we want to intercept. The problem with that approach is that base level (normal methods) and meta level (__noSuchMethod__) are mixed. Base-level code may accidentally invoke or see a meta level method and there is the possibility of accidentally defining a meta level method.
Even in standard ECMAScript 5, base level and meta level are sometimes mixed. For example, the following metaprogramming mechanisms can fail, because they exist at the base level:
obj.hasOwnProperty(propKey): This call can fail if a property in the prototype chain overrides the built-in implementation. For example, it fails if obj is:
{ hasOwnProperty: null }
A safe way to call this method is:
Object.prototype.hasOwnProperty.call(obj, propKey)
// Abbreviated version:
{}.hasOwnProperty.call(obj, propKey)
func.call(···), func.apply(···): For each of these two methods, problem and solution are the same as with hasOwnProperty.obj.__proto__: In most JavaScript engines, __proto__ is a special property that lets you get and set the prototype of obj. Hence, when you use objects as dictionaries, you must be careful to avoid __proto__ as a property key.By now, it should be obvious that making (base level) property keys special is problematic. Therefore, proxies are stratified – base level (the proxy object) and meta level (the handler object) are separate.
Proxies are used in two roles:
An earlier design of the proxy API conceived proxies as purely virtual objects. However, it turned out that even in that role, a target was useful, to enforce invariants (which is explained later) and as a fallback for traps that the handler doesn’t implement.
Proxies are shielded in two ways:
Both principles give proxies considerable power for impersonating other objects. One reason for enforcing invariants (as explained later) is to keep that power in check.
If you do need a way to tell proxies apart from non-proxies, you have to implement it yourself. The following code is a module lib.js that exports two functions: one of them creates proxies, the other one determines whether an object is one of those proxies.
// lib.js
const proxies = new WeakSet();
export function createProxy(obj) {
const handler = {};
const proxy = new Proxy(obj, handler);
proxies.add(proxy);
return proxy;
}
export function isProxy(obj) {
return proxies.has(obj);
}
This module uses the ECMAScript 6 data structure WeakSet for keeping track of proxies. WeakSet is ideally suited for this purpose, because it doesn’t prevent its elements from being garbage-collected.
The next example shows how lib.js can be used.
// main.js
import { createProxy, isProxy } from './lib.js';
const p = createProxy({});
console.log(isProxy(p)); // true
console.log(isProxy({})); // false
This section examines how JavaScript is structured internally and how the set of proxy traps was chosen.
In the context of programming languages and API design, a protocol is a set of interfaces plus rules for using them. The ECMAScript specification describes how to execute JavaScript code. It includes a protocol for handling objects. This protocol operates at a meta level and is sometimes called the meta object protocol (MOP). The JavaScript MOP consists of own internal methods that all objects have. “Internal” means that they exist only in the specification (JavaScript engines may or may not have them) and are not accessible from JavaScript. The names of internal methods are written in double square brackets.
The internal method for getting properties is called [[Get]]. If we pretend that property names with square brackets are legal, this method would roughly be implemented as follows in JavaScript.
// Method definition
[[Get]](propKey, receiver) {
const desc = this.[[GetOwnProperty]](propKey);
if (desc === undefined) {
const parent = this.[[GetPrototypeOf]]();
if (parent === null) return undefined;
return parent.[[Get]](propKey, receiver); // (A)
}
if ('value' in desc) {
return desc.value;
}
const getter = desc.get;
if (getter === undefined) return undefined;
return getter.[[Call]](receiver, []);
}
The MOP methods called in this code are:
[[GetOwnProperty]] (trap getOwnPropertyDescriptor)[[GetPrototypeOf]] (trap getPrototypeOf)[[Get]] (trap get)[[Call]] (trap apply)In line A you can see why proxies in a prototype chain find out about get if a property isn’t found in an “earlier” object: If there is no own property whose key is propKey, the search continues in the prototype parent of this.
Fundamental versus derived operations. You can see that [[Get]] calls other MOP operations. Operations that do that are called derived. Operations that don’t depend on other operations are called fundamental.
The meta object protocol of proxies is different from that of normal objects. For normal objects, derived operations call other operations. For proxies, each operation (regardless of whether it is fundamental or derived) is either intercepted by a handler method or forwarded to the target.
What operations should be interceptable via proxies? One possibility is to only provide traps for fundamental operations. The alternative is to include some derived operations. The advantage of doing so is that it increases performance and is more convenient. For example, if there weren’t a trap for get, you’d have to implement its functionality via getOwnPropertyDescriptor. One problem with derived traps is that they can lead to proxies behaving inconsistently. For example, get may return a value that is different from the value in the descriptor returned by getOwnPropertyDescriptor.
Intercession by proxies is selective: you can’t intercept every language operation. Why were some operations excluded? Let’s look at two reasons.
First, stable operations are not well suited for intercession. An operation is stable if it always produces the same results for the same arguments. If a proxy can trap a stable operation, it can become unstable and thus unreliable. Strict equality (===) is one such stable operation. It can’t be trapped and its result is computed by treating the proxy itself as just another object. Another way of maintaining stability is by applying an operation to the target instead of the proxy. As explained later, when we look at how invariants are enfored for proxies, this happens when Object.getPrototypeOf() is applied to a proxy whose target is non-extensible.
A second reason for not making more operations interceptable is that intercession means executing custom code in situations where that normally isn’t possible. The more this interleaving of code happens, the harder it is to understand and debug a program. It also affects performance negatively.
get versus invoke
If you want to create virtual methods via ECMAScript 6 proxies, you have to return functions from a get trap. That raises the question: why not introduce an extra trap for method invocations (e.g. invoke)? That would enable us to distinguish between:
obj.prop (trap get)obj.prop() (trap invoke)There are two reasons for not doing so.
First, not all implementations distinguish between get and invoke. For example, Apple’s JavaScriptCore doesn’t.
Second, extracting a method and invoking it later via call() or apply() should have the same effect as invoking the method via dispatch. In other words, the following two variants should work equivalently. If there was an extra trap invoke then that equivalence would be harder to maintain.
// Variant 1: call via dynamic dispatch
const result = obj.m();
// Variant 2: extract and call directly
const m = obj.m;
const result = m.call(obj);
invoke
Some things can only be done if you are able to distinguish between get and invoke. Those things are therefore impossible with the current proxy API. Two examples are: auto-binding and intercepting missing methods. Let’s examine how one would implement them if proxies supported invoke.
Auto-binding. By making a proxy the prototype of an object obj, you can automatically bind methods:
m via obj.m returns a function whose this is bound to obj.obj.m() performs a method call.Auto-binding helps with using methods as callbacks. For example, variant 2 from the previous example becomes simpler:
const boundMethod = obj.m;
const result = boundMethod();
Intercepting missing methods. invoke lets a proxy emulate the previously mentioned __noSuchMethod__ mechanism that Firefox supports. The proxy would again become the prototype of an object obj. It would react differently depending on how an unknown property foo is accessed:
obj.foo, no intercession happens and undefined is returned.obj.foo() then the proxy intercepts and, e.g., notifies a callback.Before we look at what invariants are and how they are enforced for proxies, let’s review how objects can be protected via non-extensibility and non-configurability.
There are two ways of protecting objects:
Non-extensibility. If an object is non-extensible, you can’t add properties and you can’t change its prototype:
'use strict'; // switch on strict mode to get TypeErrors
const obj = Object.preventExtensions({});
console.log(Object.isExtensible(obj)); // false
obj.foo = 123; // TypeError: object is not extensible
Object.setPrototypeOf(obj, null); // TypeError: object is not extensible
Non-configurability. All the data of a property is stored in attributes. A property is like a record and attributes are like the fields of that record. Examples of attributes:
value holds the value of a property.writable controls whether a property’s value can be changed.configurable controls whether a property’s attributes can be changed.Thus, if a property is both non-writable and non-configurable, it is read-only and remains that way:
'use strict'; // switch on strict mode to get TypeErrors
const obj = {};
Object.defineProperty(obj, 'foo', {
value: 123,
writable: false,
configurable: false
});
console.log(obj.foo); // 123
obj.foo = 'a'; // TypeError: Cannot assign to read only property
Object.defineProperty(obj, 'foo', {
configurable: true
}); // TypeError: Cannot redefine property
For more details on these topics (including how Object.defineProperty() works) consult the following sections in “Speaking JavaScript”:
Traditionally, non-extensibility and non-configurability are:
These and other characteristics that remain unchanged in the face of language operations are called invariants. With proxies, it is easy to violate invariants, as they are not intrinsically bound by non-extensibility etc.
The proxy API prevents proxies from violating invariants by checking the parameters and results of handler methods. The following are four examples of invariants (for an arbitrary object obj) and how they are enforced for proxies (an exhaustive list is given at the end of this chapter).
The first two invariants involve non-extensibility and non-configurability. These are enforced by using the target object for bookkeeping: results returned by handler methods have to be mostly in sync with the target object.
Object.preventExtensions(obj) returns true then all future calls must return false and obj must now be non-extensible.
TypeError if the handler returns true, but the target object is not extensible.Object.isExtensible(obj) must always return false.
TypeError if the result returned by the handler is not the same (after coercion) as Object.isExtensible(target).The remaining two invariants are enforced by checking return values:
Object.isExtensible(obj) must return a boolean.
Object.getOwnPropertyDescriptor(obj, ···) must return an object or undefined.
TypeError if the handler doesn’t return an appropriate value.Enforcing invariants has the following benefits:
The next two sections give examples of invariants being enforced.
In response to the getPrototypeOf trap, the proxy must return the target’s prototype if the target is non-extensible.
To demonstrate this invariant, let’s create a handler that returns a prototype that is different from the target’s prototype:
const fakeProto = {};
const handler = {
getPrototypeOf(t) {
return fakeProto;
}
};
Faking the prototype works if the target is extensible:
const extensibleTarget = {};
const ext = new Proxy(extensibleTarget, handler);
console.log(Object.getPrototypeOf(ext) === fakeProto); // true
We do, however, get an error if we fake the prototype for a non-extensible object.
const nonExtensibleTarget = {};
Object.preventExtensions(nonExtensibleTarget);
const nonExt = new Proxy(nonExtensibleTarget, handler);
Object.getPrototypeOf(nonExt); // TypeError
If the target has a non-writable non-configurable property then the handler must return that property’s value in response to a get trap. To demonstrate this invariant, let’s create a handler that always returns the same value for properties.
const handler = {
get(target, propKey) {
return 'abc';
}
};
const target = Object.defineProperties(
{}, {
foo: {
value: 123,
writable: true,
configurable: true
},
bar: {
value: 456,
writable: false,
configurable: false
},
});
const proxy = new Proxy(target, handler);
Property target.foo is not both non-writable and non-configurable, which means that the handler is allowed to pretend that it has a different value:
However, property target.bar is both non-writable and non-configurable. Therefore, we can’t fake its value:
enumerate trap? ES6 originally had a trap enumerate that was triggered by for-in loops. But it was recently removed, to simplify proxies. Reflect.enumerate() was removed, as well. (Source: TC39 notes)
This section serves as a quick reference for the proxy API: the global objects Proxy and Reflect.
There are two ways to create proxies:
const proxy = new Proxy(target, handler)const {proxy, revoke} = Proxy.revocable(target, handler)revoke. revoke can be called multiple times, but only the first call has an effect and switches proxy off. Afterwards, any operation performed on proxy leads to a TypeError being thrown.This subsection explains what traps can be implemented by handlers and what operations trigger them. Several traps return boolean values. For the traps has and isExtensible, the boolean is the result of the operation. For all other traps, the boolean indicates whether the operation succeeded or not.
Traps for all objects:
defineProperty(target, propKey, propDesc) : boolean
Object.defineProperty(proxy, propKey, propDesc)deleteProperty(target, propKey) : boolean
delete proxy[propKey]delete proxy.foo // propKey = 'foo'get(target, propKey, receiver) : any
receiver[propKey]receiver.foo // propKey = 'foo'getOwnPropertyDescriptor(target, propKey) : PropDesc|Undefined
Object.getOwnPropertyDescriptor(proxy, propKey)getPrototypeOf(target) : Object|Null
Object.getPrototypeOf(proxy)has(target, propKey) : boolean
propKey in proxyisExtensible(target) : boolean
Object.isExtensible(proxy)ownKeys(target) : Array<PropertyKey>
Object.getOwnPropertyPropertyNames(proxy) (only uses string keys)Object.getOwnPropertyPropertySymbols(proxy) (only uses symbol keys)Object.keys(proxy) (only uses enumerable string keys; enumerability is checked via Object.getOwnPropertyDescriptor)preventExtensions(target) : boolean
Object.preventExtensions(proxy)set(target, propKey, value, receiver) : boolean
receiver[propKey] = valuereceiver.foo = value // propKey = 'foo'setPrototypeOf(target, proto) : boolean
Object.setPrototypeOf(proxy, proto)Traps for functions (available if target is a function):
apply(target, thisArgument, argumentsList) : any
proxy.apply(thisArgument, argumentsList)proxy.call(thisArgument, ...argumentsList)proxy(...argumentsList)construct(target, argumentsList, newTarget) : Object
new proxy(..argumentsList)The following operations are fundamental, they don’t use other operations to do their work: apply, defineProperty, deleteProperty, getOwnPropertyDescriptor, getPrototypeOf, isExtensible, ownKeys, preventExtensions, setPrototypeOf
All other operations are derived, they can be implemented via fundamental operations. For example, for data properties, get can be implemented by iterating over the prototype chain via getPrototypeOf and calling getOwnPropertyDescriptor for each chain member until either an own property is found or the chain ends.
Invariants are safety constraints for handlers. This subsection documents what invariants are enforced by the proxy API and how. Whenever you read “the handler must do X” below, it means that a TypeError is thrown if it doesn’t. Some invariants restrict return values, others restrict parameters. The correctness of a trap’s return value is ensured in two ways: Normally, an illegal value means that a TypeError is thrown. But whenever a boolean is expected, coercion is used to convert non-booleans to legal values.
This is the complete list of invariants that are enforced:
apply(target, thisArgument, argumentsList)
construct(target, argumentsList, newTarget)
null or a primitive value).defineProperty(target, propKey, propDesc)
propKey must be one of the own keys of the target.propDesc sets the attribute configurable to false then the target must have a non-configurable own property whose key is propKey.propDesc were to be used to (re)define an own property for the target then that must not cause an exception. An exception is thrown if a change is forbidden by the attributes writable and configurable (non-extensibility is handled by the first rule).deleteProperty(target, propKey)
get(target, propKey, receiver)
propKey then the handler must return that property’s value.undefined.getOwnPropertyDescriptor(target, propKey)
undefined.writable and configurable (non-extensibility is handled by the third rule). Therefore, the handler can’t report a non-configurable property as configurable and it can’t report a different value for a non-configurable non-writable property.getPrototypeOf(target)
null.has(target, propKey)
isExtensible(target)
target.isExtensible().ownKeys(target)
preventExtensions(target)
target.isExtensible() must be false afterwards.set(target, propKey, value, receiver)
propKey then value must be the same as the value of that property (i.e., the property can’t be changed).TypeError is thrown (i.e., such a property can’t be set).setPrototypeOf(target, proto)
proto must be the same as the prototype of the target. Otherwise, a TypeError is thrown.The following operations of normal objects perform operations on objects in the prototype chain. Therefore, if one of the objects in that chain is a proxy, its traps are triggered. The specification implements the operations as internal own methods (that are not visible to JavaScript code). But in this section, we pretend that they are normal methods that have the same names as the traps. The parameter target becomes the receiver of the method call.
target.get(propertyKey, receiver)target has no own property with the given key, get is invoked on the prototype of target.target.has(propertyKey)get, has is invoked on the prototype of target if target has no own property with the given key.target.set(propertyKey, value, receiver)get, set is invoked on the prototype of target if target has no own property with the given key.All other operations only affect own properties, they have no effect on the prototype chain.
The global object Reflect implements all interceptable operations of the JavaScript meta object protocol as methods. The names of those methods are the same as those of the handler methods, which, as we have seen, helps with forwarding operations from the handler to the target.
Reflect.apply(target, thisArgument, argumentsList) : anyFunction.prototype.apply().Reflect.construct(target, argumentsList, newTarget=target) : Objectnew operator as a function. target is the constructor to invoke, the optional parameter newTarget points to the constructor that started the current chain of constructor calls. More information on how constructor calls are chained in ES6 is given in the chapter on classes.Reflect.defineProperty(target, propertyKey, propDesc) : booleanObject.defineProperty().Reflect.deleteProperty(target, propertyKey) : booleandelete operator as a function. It works slightly differently, though: It returns true if it successfully deleted the property or if the property never existed. It returns false if the property could not be deleted and still exists. The only way to protect properties from deletion is by making them non-configurable. In sloppy mode, the delete operator returns the same results. But in strict mode, it throws a TypeError instead of returning false.Reflect.get(target, propertyKey, receiver=target) : anyreceiver is needed when get reaches a getter later in the prototype chain. Then it provides the value for this.Reflect.getOwnPropertyDescriptor(target, propertyKey) : PropDesc|UndefinedObject.getOwnPropertyDescriptor().Reflect.getPrototypeOf(target) : Object|NullObject.getPrototypeOf().Reflect.has(target, propertyKey) : booleanin operator as a function.Reflect.isExtensible(target) : booleanObject.isExtensible().Reflect.ownKeys(target) : Array<PropertyKey>Reflect.preventExtensions(target) : booleanObject.preventExtensions().Reflect.set(target, propertyKey, value, receiver=target) : booleanReflect.setPrototypeOf(target, proto) : boolean__proto__.Several methods have boolean results. For has and isExtensible, they are the results of the operation. For the remaining methods, they indicate whether the operation succeeded.
Reflect besides forwarding Apart from forwarding operations, why is Reflect useful [4]?
Reflect duplicates the following methods of Object, but its methods return booleans indicating whether the operation succeeded (where the Object methods return the object that was modified).
Object.defineProperty(obj, propKey, propDesc) : ObjectObject.preventExtensions(obj) : ObjectObject.setPrototypeOf(obj, proto) : ObjectReflect methods implement functionality that is otherwise only available via operators:
Reflect.construct(target, argumentsList, newTarget=target) : ObjectReflect.deleteProperty(target, propertyKey) : booleanReflect.get(target, propertyKey, receiver=target) : anyReflect.has(target, propertyKey) : booleanReflect.set(target, propertyKey, value, receiver=target) : booleanapply(): If you want to be completely safe about invoking the method apply() on a function, you can’t do so via dynamic dispatch, because the function may have an own property with the key 'apply':
func.apply(thisArg, argArray) // not safe
Function.prototype.apply.call(func, thisArg, argArray) // safe
Using Reflect.apply() is shorter:
Reflect.apply(func, thisArg, argArray)
delete operator throws in strict mode if you try to delete a non-configurable own property. Reflect.deleteProperty() returns false in that case.Object.* versus Reflect.*
Going forward, Object will host operations that are of interest to normal applications, while Reflect will host operations that are more low-level.
This concludes our in-depth look at the proxy API. For each application, you have to take performance into consideration and – if necessary – measure. Proxies may not always be fast enough. On the other hand, performance is often not crucial and it is nice to have the metaprogramming power that proxies give us. As we have seen, there are numerous use cases they can help with.
[1] “On the design of the ECMAScript Reflection API” by Tom Van Cutsem and Mark Miller. Technical report, 2012. [Important source of this chapter.]
[2] “The Art of the Metaobject Protocol” by Gregor Kiczales, Jim des Rivieres and Daniel G. Bobrow. Book, 1991.
[3] “Putting Metaclasses to Work: A New Dimension in Object-Oriented Programming” by Ira R. Forman and Scott H. Danforth. Book, 1999.
[4] “Harmony-reflect: Why should I use this library?” by Tom Van Cutsem. [Explains why Reflect is useful.]