| 06:18 | <Domenic> | I think this is a Node.js bug: a Proxy with get(target, property, receiver) { return Reflect.get(target, property, receiver); } should not cause different behavior than one with no handlers. Even if that Proxy is being used as a global object. But I would love it if an ECMAScript expert was able to weigh in on the thread and confirm. |
| 08:26 | <Rob Palmer> | Where is the Node Proxy thread? |
| 08:51 | <Domenic> | Wow, sorry, totally forgot the actual link... https://github.com/nodejs/node/issues/54550 |
| 22:47 | <snek> | Wow, sorry, totally forgot the actual link... https://github.com/nodejs/node/issues/54550 |
| 22:47 | <snek> | i also found some bugs in v8 and those fixes might not have made it to versions of node you're using yet |
| 22:47 | <snek> | or any versions of node, they track upstream v8 a lot more slowly |
| 23:08 | <snek> | i guess more concretely, introducing an object environment record using with and the proxy in your issue does not behave strangely in v8, its only the vm code that uses interceptors that is weird. |