The native Node modules are supported by Electron, but since Electron is using a different V8 version from official Node, you have to manually specify the location of Electron's headers when building native modules.
See https://github.com/atom/electron/blob/master/docs/tutorial/using-native-node-modules.md for more details.
ironNode uses electron-recompile which aims to help to compile native modules for a specific electron version. Normaly it depends on the Node.js module if you can manage different native versions at the same time.
I implemented both electron-recompile and Node Module Path to implement a "re-compile" feature.
By calling iron-node --compile[=your-node-project-path] you can recompile all native modules in the node_modules subfolder or the current workking directory against the current installed iron-node v8 version.
If you ever get an error while loading native node modules you can activate an overwrite of the internal node require function. You can make use of native+ option after you have re-compiled all native modules in your node project folder with iron-node --compile. So far this option needs manual activation. May be it defaults to true in future. Once we have figured out that it is not dangerous 😳.
See Local and global configuration to learn how to configure the .iron-node.js configuration file.
- Install node.js
- Install Python 2.7
- Install .NET Framework to get VCBuild.exe
- npm config set msvs_version 2015 --global to set msvs_version
- npm install node-gyp #https://github.com/nodejs/node-gyp#installation