From dd28a2ef146343c96878d8957c0bf58697c3b3d1 Mon Sep 17 00:00:00 2001 From: Brandon Nozaki Miller Date: Fri, 28 Aug 2015 14:16:05 -0700 Subject: [PATCH] Update documentation to clarify bundled node/io.js version --- docs/tutorial/using-native-node-modules.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/tutorial/using-native-node-modules.md b/docs/tutorial/using-native-node-modules.md index 6b9631296f4c..918c8a67a94a 100644 --- a/docs/tutorial/using-native-node-modules.md +++ b/docs/tutorial/using-native-node-modules.md @@ -7,14 +7,14 @@ the location of Electron's headers when building native modules. ## Native Node module compatibility Since Node v0.11.x there were vital changes in the V8 API. So generally all -native modules written for Node v0.10.x wouldn't work for Node v0.11.x. And -because Electron internally uses Node v0.11.13, it carries with the same +native modules written for Node v0.10.x wouldn't work for newer Node or io.js versions. And +because Electron internally uses __io.js v3.1.0__, it carries with the same problem. -To solve this, you should use modules that support Node v0.11.x, +To solve this, you should use modules that support Node v0.11.x or later, [many modules](https://www.npmjs.org/browse/depended/nan) do support both now. For old modules that only support Node v0.10.x, you should use the -[nan](https://github.com/rvagg/nan) module to port it to v0.11.x. +[nan](https://github.com/rvagg/nan) module to port it to v0.11.x or later versions of Node or io.js. ## How to install native modules