This is a shim for the ECMAScript 6 Reflect and Proxy objects.

Read Why should I use this library?

Installation

If you are using node.js (>= v0.7.8), you can install via npm:

npm install harmony-reflect

Then:

node --harmony_proxies
> var Reflect = require('harmony-reflect');

See release notes for changes to the npm releases.

To use in a browser, just download the single reflect.js file. After loading

<script src="reflect.js"></script>

a global object Reflect is defined that contains reflection methods as defined in the ES6 draft.

If your browser supports the "harmony-era" Proxy object that predates ES6 (i.e. Firefox or Chrome <= v37), that Proxy object is also updated to follow the latest direct proxies spec. To create such a proxy, call:

var proxy = new Proxy(target, handler)

API Docs

This module exports an object named Reflect and updates the global Proxy object (if it exists) to be compatible with the latest ECMAScript 6 spec.

The ECMAScript 6 Proxy API allows one to intercept various operations on Javascript objects.

• Overview of all supported traps on proxies
• The Reflect API
• The Proxy Handler API

Compatibility

The Reflect API, with support for proxies, was tested on:

• Firefox (>= v4.0)
• node --harmony_proxies (>= v0.7.8)
• iojs --harmony_proxies (>= 2.3.0)
• v8 --harmony_proxies (>= v3.6)
• Any recent js spidermonkey shell

Note:

• Chrome (>= v19 && <= v37) used to support proxies behind a flag (chrome://flags/#enable-javascript-harmony) but Chrome v38 removed the Proxy constructor. As a result, this library cannot patch the harmony-era Proxy object on Chrome v38 or above. If you're working with chromium directly, it's still possible to enable proxies using chromium-browser --js-flags="--harmony_proxies".
• In earlier versions of v8, the Proxy constructor was enabled by default when starting v8 with --harmony. For recent versions of v8, Proxy must be explicitly enabled with --harmony_proxies.

Dependencies

• ECMAScript 5/strict
• To emulate direct proxies: * old Harmony Proxies * Harmony WeakMaps

After loading reflect.js into your page or other JS environment, be aware that the following globals are patched to be able to recognize emulated direct proxies:

Object.getOwnPropertyDescriptor
Object.defineProperty
Object.defineProperties
Object.getOwnPropertyNames
Object.keys
Object.{get,set}PrototypeOf
Object.{freeze,seal,preventExtensions}
Object.{isFrozen,isSealed,isExtensible}
Object.prototype.valueOf
Object.prototype.isPrototypeOf
Object.prototype.toString
Object.prototype.hasOwnProperty
Function.prototype.toString
Date.prototype.toString
Array.isArray
Array.prototype.concat
Proxy
Reflect

⚠️ In node.js, when you require('harmony-reflect'), only the current module's globals are patched. If you pass an emulated direct proxy to an external module, and that module uses the unpatched globals, the module may not interact with the proxy according to the latest ES6 Proxy API, instead falling back on the old pre-ES6 Proxy API. This can cause bugs, e.g. the built-in Array.isArray will return false when passed a proxy-for-array, while the patched Array.isArray will return true. I know of no good fix to reliably patch the globals for all node modules. If you do, let me know.

Examples

The examples directory contains a number of examples demonstrating the use of proxies:

• membranes: wrappers that transitively isolate two object-graphs.
• observer: a self-hosted implementation of the ES7 Object.observe notification mechanism.
• profiler: a simple profiler to collect usage statistics of an object.

Other example uses of proxies (not done by me, but using this library):

• supporting negative array indices a la Python
• tpyo: using proxies to correct typo's in JS property names
• persistent objects: shows how one might go about using proxies to save updates to objects in a database incrementally

For more examples of proxies, and a good overview of their design rationale, I recommend reading Axel Rauschmayer's blog post on proxies.

Proxy Handler API

The sister project proxy-handlers defines a number of predefined Proxy handlers as "abstract classes" that your code can "subclass" The goal is to minimize the number of traps that your proxy handlers must implement.

Spec Compatibility

This library differs from the rev 27 (august 2014) draft ECMAScript 6 spec as follows:

• In ES6, Proxy will be a constructor function that will require the use of new. That is, you must write new Proxy(target, handler). This library exports Proxy as an ordinary function which may be called with or without using the new operator.
• Array.isArray(obj) and [].concat(obj) are patched so they work transparently on proxies-for-arrays (e.g. when obj is new Proxy([],{})). The current ES6 draft spec does not treat proxies-for-arrays as genuine arrays for these operations. Update (Nov. 2014): it looks like the ES6 spec will change so that Array.isArray and other methods that test for arrayness will work transparently on proxies, so this shim's behavior will become the standardized behavior.