Reference Error: Proxy is Not Defined

Question

I am trying to use ES6 Proxies in an Angular app of mine as so:

// Create defensive object using ES6 Proxy
createDefensiveObject(target) {

  return new Proxy(target, {

    get : (target, property) => {

      if(property in target) 
        return target[property];

      else
        throw new ReferenceError(`Property \"${property}\" does not exist`);
    }
  });
}

I am using Traceur to transpile everything in Chrome, and I have experimental JavaScript enabled. All other ES6 features I have implemented are working as expected, but with Proxies I get : Reference Error: Proxy is not defined

Any insight?

datatype_void · Accepted Answer · 2015-07-10 19:52:17Z

2

Referencing this table here it would seem that Traceur has no support for ES6 proxies at this time. Babel which I use to transpile back-end code also has no support. It looks as though io.js has limited support, so further research will have to be done in order to determine whether that solution will be suitable to our needs. Though this won't help my Angular front-end.

edited Jul 10, 2015 at 19:52

answered Jul 10, 2015 at 19:47

datatype_void

4435 silver badges23 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

loganfsmyth Over a year ago

Proxy is one of the ES6 features that cannot be polyfilled unfortunately.

datatype_void Over a year ago

I managed to find a polyfill called harmony-reflect, but Chrome has zero Proxy support outside of enabling some Chromium flags from what I understand. Which makes it useless for my case.

loganfsmyth Over a year ago

Yeah that only makes old proxies follow the spec, it doesn't add support for Proxy where there is none unfortunately.

Collectives™ on Stack Overflow

Reference Error: Proxy is Not Defined

1 Answer 1

3 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related