ksp4186

True. I think it will pick up once Node.js + Chakracore (or other Javascript Engines) starts taking momentum.

For native modules, below options are ideal: - V8 C++ API : These APIs will continue to work with node.js v8 as well as with Chakra because in shim layer we map them to equivalent Chakra APIs. If you see problem in any APIs not working as expected using Chakra engine, please file an issue on Microsoft/node and we will happy to fix it. - NAN : Node.js Chakra is compatible with latest NAN version so it should continue to work with V8 and Chakra engine.

Regarding, Node inbuilt native functions (in other works deps) that are independent of v8, continue to work in Chakra without reimplementation. Chakra shim comes into picture to map V8 C++ APIs to Chakra equivalent.

Its a long goal as of now that everyone want to achieve. You can follow this discussion at https://github.com/nodejs/nan/issues/349

We are basing it off nodejs/master - https://github.com/nodejs/node

That's correct. V8 license is required in v8-*.h files because they are v8 header files that chakra shim uses. The implementation files has Microsoft license.

E.g. All files in https://github.com/Microsoft/node/tree/chnext/deps/chakrashi...

Disclaimer: I work for Chakra team (powering node.js)

Microsoft is already working on lighting Node.js with ChakraCore.

See https://github.com/Microsoft/node