I've seen some confusion from devs related to the supported OSs for ChakraNode.
I think it comes down to the readme having notes about Unix/Macintosh.

This could be resolved with a more explicit message about support.

The lodash unit tests call require('vm').runInNewContext(...); which causes a fatal error:

Assertion failed: false, file src\jsrtcrosscontext.cc, line 48.

I'm aware that support for the vm module isn't all there yet but I assumed it would just throw a JS error that I could catch.

In the configure script, the PYTHON variable is missing quotes around it (PYTHON=c:\Program Files\Python\python). This causes problems compiling the code on Windows 8.1

Thank you!

Given most native addons use the V8 APIs, is there any plans from Microsoft to either contribute something to nan, so that it allows addons to be compatible with Chakra, or some guidelines to port native modules?

Also #9 is relevant too at this point.

Dear,

Why wouldn't we just create a script called npm.cmd like in the legacy nodeJS and add it to the path ?

:: Created by npm, please don't edit manually.
@IF EXIST "%~dp0\node.exe" (
  "%~dp0\node.exe" "%~dp0\.\node_modules\npm\bin\npm-cli.js" %*
) ELSE (
  node "%~dp0\.\node_modules\npm\bin\npm-cli.js" %*
)

With that kind of script, we will be able to use :

npm install package

I noticed some issues with patchTypedArrays.

The additions are missing toString functions that mimic their original built-ins, e.g.
function slice() { [native code] }, and instead return their shim source.

This affects lodash's check to see whether ArrayBuffer#slice is built-in:

_.isNative(ArrayBuffer.prototype.slice);
// => false

I also noticed issues with the overwritten TypedArray#set method. It performs a first instanceof Array check which causes set not to work correctly when passed a typed array.

I'm not sure why the methods are wrapped but they could hold a reference to their original method and defer to it when not needing the custom behavior. For example:

Float64Array.prototype.set = (function(func) {
  function set(array) {
    var offset = arguments[1];
    if (somethingToBranchFor) {
      /* do custom stuff */
    }
    return func.apply(this, arguments);
 }

 function toString() {
   return func.toString();
 }
 Object.defineProperty(set, 'toString', Object.getOwnPropertyDescriptor(func, 'toString')); 
 return set;
}(Float64Array.prototype.set));

Hello, I apologize if this isn't the right place to post this, but I've been trying to build the curve25519 addon and I keep coming up with a lot of errors.
Most of the errors seem related to v8 files. Could you point me in the rigth direction?

Here are the error I got:

and here the code that doesn't compile:

Wonder if this node support serialport and Bluetooth Low Energy APIs on Windows 10? i.e Windows 10 on Raspberry Pi and PC?

I see there's process.versions.chakra with a value of 11.0.10056.0 and wondering what it maps to.
Is that really the version number?

Hey, I noticed this fork is 5 years old. Are there any plans to archive this repo or delete it?

Reproduced it on two Win10/x64 PCs after updating them to ver 1511.
Was able to fix it by the following change to chakra_shim.js:

    diff --git a/deps/chakrashim/lib/chakra_shim.js b/deps/chakrashim/lib/chakra_shim.js
    index 29adee1..79d287c 100644
    --- a/deps/chakrashim/lib/chakra_shim.js
    +++ b/deps/chakrashim/lib/chakra_shim.js
    @@ -390,8 +390,8 @@
           arr.push(Object_getOwnPropertyDescriptor(x, 'caller').get);

           var x = createEmptyStrictModeFunction();
    -      arr.push(Object_getOwnPropertyDescriptor(x, 'caller').get);
    -      arr.push(Object_getOwnPropertyDescriptor(x, 'arguments').get);
    +      arr.push(Object_getOwnPropertyDescriptor(x.__proto__, 'caller').get);
    +      arr.push(Object_getOwnPropertyDescriptor(x.__proto__, 'arguments').get);
           arr.push(Object_getOwnPropertyDescriptor(x(), 'callee').get);

           return arr;

This is most probably an underlying engine (chakra) issue instead of the interface. Below code would end up showing out of memory error for V8(node/jxcore), works without a problem for SpiderMonkey(jxcore) and shows undefined behavior for chakra build.

jx / node.exe -pe "var arr=new Array(1e8); for(var i=0;i<1e8;i++) arr[i]=2 + (i%2); arr[1e6]"

produces undefined on ARM. If I check the value for arr[1e3], the result is 2 as expected. I would expect either out of memory error or showing the same result for both indexes.

Am I missing a point here ?

I have build this code under windows 10 with newest update and vs2015 with update 1, and Node.js Tools for Windows IoT has been installed, there is still a wrong sdk version error. I check the v8.h and find that the macro CHAKRART_H has not been declared

I would like to use ES6 features under flag like --harmony .
How do I set the flag??

We use FunctionTemplate::Inherit to export C++ complex class to javascript in our game engine . thanks

haha

Hello, I apologize if this isn't the right place to post this, But I've been trying to build this and I keep coming up with tons of errors

I have all the prerequisites except for Windows 10 tools, which this page said was included with VS 2015
https://dev.windows.com/en-us/downloads/windows-10-developer-tools

Most of the errors/warnings are about v8 files, could anyone point me in the right direction?

Everyone I've talked to so far would like to find a way to get this merged in to node.js upstream.

What do we need to do? @nodejs/Collaborators @nodejs/TSC

Currently, this project lacks of major open source documentations and clarifications.

There's no hint that chakra will ever be open source, so that is kind of a hard issue.
Another issue is that Windows (at least IoT) uses explicitely whitelisted dlls, which may be required for other JIT compilers/runtimes.

Is there any way to use your own JIT in Win10?
I bet the community will deny a forced JIT (if it's not open source), as this is quality level of iOS. And to be honest, it can't get worse than that.

So, please clarify the usage of chakra here. It is nice to see API bindings for Chakra, but they won't have a real-world usecase if the JS engine can't be fixed and be maintained properly with the nodejs / iojs API and occuring bugs.