Jimmy Thomson
Jimmy Thomson
Is this only guaranteed to be precise for 52 bit numbers?
Thanks for reporting this. I believe that this is because we still only have partial support for the chrome inspector protocol. We have better compatibility with VSCode's usage of the...
Once we do get our support for modules into a state that node-chakracore can use, we need to re-enable a number of tests in `test/parallel`. Some new tests of `vm`...
The windows test failure was a bug in the shim that was fixed a short time ago.
Thanks for reporting this @dpogue; ChakraCore doesn't provide all the hooks that node expects for es6 modules, so right now node-chakracore does not support them. We're working on adding support...
See https://github.com/nodejs/node-chakracore/issues/391 for some more details.
I believe this is the same as the chakracore issue https://github.com/Microsoft/ChakraCore/issues/2512
Looks like this is because of how we try to create a v8-style context. Within the context, we create a proxy and assign it as the prototype of the global...
Ah nevermind, I was mis-using `hasOwnProperty`; should have been `this.hasOwnProperty('a')` and then it works as expected. It seems that the main downfall of our current approach is the fact that...
I believe that for a proper fix here we'll need to add support for interceptors on the global object / having a proxy as a global object. Without going that...