most recent 30 from stackoverflow.com 2025-08-04T12:54:50Z https://stackoverflow.com/feeds/question/74418853 https://creativecommons.org/licenses/by-sa/4.0/rdf https://stackoverflow.com/q/74418853 2 Tanin https://stackoverflow.com/users/710895 2025-08-04T06:06:54Z 2025-08-04T18:14:22Z

<p>For example, <a href="https://www.npmjs.com/package/electron-releases" rel="nofollow noreferrer">https://www.npmjs.com/package/electron-releases</a> states that v19.1.3 has NODE_MODULE_VERSION as 106 and Node's version as 16.14.2.</p> <p>But <a href="https://nodejs.org/en/download/releases/" rel="nofollow noreferrer">https://nodejs.org/en/download/releases/</a> states that Node 16.14.2 corresponds to NODE_MODULE_VERSION 93.</p> <p>Stepping back, I'm trying to avoid the error <code>was compiled against a different Node.js version using NODE_MODULE_VERSION 93. This version of Node.js requires NODE_MODULE_VERSION 106. Please try re-compiling or re-installing</code>.</p> <p>While I can rebuild, I wonder why Electron's NODE_MODULE_VERSION doesn't seem to follow Node's guideline and possibly solve this hiccup in some way.</p> <p>Thank you.</p>

https://stackoverflow.com/questions/74418853/-/74419901#74419901 2 Alexander Leithner https://stackoverflow.com/users/6786876 2025-08-04T09:48:30Z 2025-08-04T09:48:30Z

<p>This error is unavoidable since Electron uses different Node ABI versions <a href="https://www.electronjs.org/docs/latest/tutorial/using-native-node-modules" rel="nofollow noreferrer">on purpose</a>. The linked documentation states that this is because Electron differs from Node.js because of additions and modifications for using Chromium from the Node.js context, such as the use of BoringSSL instead of OpenSSL.</p> <p>Thus, you have to rebuild native modules in order to match Electron's ABI version as well as to prepare these modules (just in case) to link against BoringSSL and not OpenSSL as they might expect.</p>

百度