Error module version mismatch

Am 02.08.2016 um 13:06 schrieb JMishou notifications@github.com:

App threw an error during load
Error: Module version mismatch. Expected 49, got 48.
at Error (native)
at process.module.(anonymous function) as dlopen
at Object.Module._extensions..node (module.js:568:18)
at Object.module.(anonymous function) as .node
at Module.load (module.js:458:32)
at tryModuleLoad (module.js:417:12)
at Function.Module._load (module.js:409:3)
at Module.require (module.js:468:17)
at require (internal/module.js:20:19)
at Object. (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/wiring-pi/lib/exports.js:1:97)
Error: Module version mismatch. Expected 49, got 48.
at Error (native)
at process.module.(anonymous function) as dlopen
at Object.Module._extensions..node (module.js:568:18)
at Object.module.(anonymous function) as .node
at Module.load (module.js:458:32)
at tryModuleLoad (module.js:417:12)
at Function.Module._load (module.js:409:3)
at Module.require (module.js:468:17)
at require (internal/module.js:20:19)
at Object. (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/wiring-pi/lib/exports.js:1:97)

Unless I am reading this wrong this is expecting a Node module version that is not released yet?

The current module release is 48 https://nodejs.org/en/download/releases/ https://nodejs.org/en/download/releases/
I have tried node version v6.3.0, 6.3.1, and 5.12.0.

I have followed all of your suggestions here even though that a downgrade to a previous version and not an upgrade to an unreleased version.. #2 #2
I have tried reinstalling electron, rebuilding it, removing the module folder and re cloning it. I’m at a loss.

The only other instance of this I could find is here don/node-eddystone-beacon#40 don/node-eddystone-beacon#40 Electron-rebuild seemed to work in their case. Not so much for me.

Got any suggestions? Much appreciated.

-Jason.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub #9, or mute the thread https://github.com/notifications/unsubscribe-auth/AA8mOou6_FKonvdGI1i8lQf-38E-dwdvks5qbyTCgaJpZM4Jafsm.

Error: Module version mismatch. Expected 48, got 57. #166

Running ijsnotebook after ijsinstall . But got this error:

While running ipython notebook succeed.

The text was updated successfully, but these errors were encountered:

That error message often happens when the node version in a machine has been updated. In your case, it looks like you’ve installed IJavascript using Node v6, and now you’re trying to run it using Node v8. If this is the case, uninstalling IJavascript and installing it again should fix the problem.

Thanks for you answer. But issue still exits.

Here is my local node versions:

And run nvm use system still throw this error.

And run nvm use system still throw this error.

Without seeing the commands you run and their output I can’t help much.

Having said that, since your environment uses multiple multiple node versions, I’d suggest you install IJavascript’s kernelspec using full paths; like this:

I also encounter this issue even if I tried uninstall and install with ijsinstall —spec-path=full .

@shunmian I’ll try to help, but please, could you post the commands you’re running and their output?

@n-riesco , thanks for your time! The command I run is

, which is exactly the one documented in the README.MD for macOS.

@shunmian Those are the instructions for a fresh install. The error reported in this issue only happens when node.js has been updated after running ijsinstall ; for example, like this:

• install Node v6
• npm install -g ijavascript
• ijsinstall
• update to Node v8
• error: Error: Module version mismatch. Expected 48, got 57.

I’m sorry but I don’t have enough information to help you.

I tried reinstalling and installing zeromq, ijavascript, rebuilding, using ijsinstall —spec-path=full , I updated node and tried again — nothing works. I still get:

node -v v11.9.0
npm -v 6.5.0
macOS 10.13.6
I’m using anaconda, latest version, installed today.

What should I try to do with this, @n-riesco ?

@panpiotrs, the log message is telling us that you’re running node v11 , but IJavaScript was installed using node v5 .

Without knowing the details, I’m guessing you’ve used sudo npm install -g ijavascript to install IJavaScript. Do you really need to use sudo ? If so, what do you get when you run sudo npm —versions ?

I didn’t use sudo . After sudo npm —versions I see the same versions of npm and node → 6.5.0 and 11.9.0, and some other packages, v8, openssl, etc, nothing related to the problem.
I’m upgrading node with current (never lts) package from https://nodejs.org/ . Before today I had v9, I have no idea where this v5 is coming from.

@panpiotrs The log message shows IJavascript is installed under /usr/local/lib/node_modules/ . Doesn’t that require admin rights in macOS?

I’d try and get rid of /usr/local/lib/node_modules/ijavascript :

• either, rename it: sudo mv /usr/local/lib/node_modules/ijavascript /usr/local/lib/node_modules/ijavascript.old
• or delete it: sudo rm -rf /usr/local/lib/node_modules/ijavascript

And just to be sure, I’d install IJavascript again: npm install -g ijavascript

If zeromq is rebuilt, you should see the following lines:

Источник

Error: Module version mismatch. Expected 49, got 48. #9

App threw an error during load
Error: Module version mismatch. Expected 49, got 48.
at Error (native)
at process.module.(anonymous function) as dlopen
at Object.Module._extensions..node (module.js:568:18)
at Object.module.(anonymous function) as .node
at Module.load (module.js:458:32)
at tryModuleLoad (module.js:417:12)
at Function.Module._load (module.js:409:3)
at Module.require (module.js:468:17)
at require (internal/module.js:20:19)
at Object. (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/wiring-pi/lib/exports.js:1:97)
Error: Module version mismatch. Expected 49, got 48.
at Error (native)
at process.module.(anonymous function) as dlopen
at Object.Module._extensions..node (module.js:568:18)
at Object.module.(anonymous function) as .node
at Module.load (module.js:458:32)
at tryModuleLoad (module.js:417:12)
at Function.Module._load (module.js:409:3)
at Module.require (module.js:468:17)
at require (internal/module.js:20:19)
at Object. (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/wiring-pi/lib/exports.js:1:97)

Unless I am reading this wrong this is expecting a Node module version that is not released yet?

I have tried node version v6.3.0, 6.3.1, and 5.12.0.

I have followed all of your suggestions here even though that a downgrade to a previous version and not an upgrade to an unreleased version.. #2

I have tried reinstalling electron, rebuilding it, removing the module folder and re cloning it. I’m at a loss.

The only other instance of this I could find is here don/node-eddystone-beacon#40 Electron-rebuild seemed to work in their case. Not so much for me.

Got any suggestions? Much appreciated.

The text was updated successfully, but these errors were encountered:

This error normally comes when you run npn install inside the module folder on another node version you are using now to run the script. Try running npm install again in the module directory.

App threw an error during load
Error: Module version mismatch. Expected 49, got 48.
at Error (native)
at process.module.(anonymous function) as dlopen
at Object.Module._extensions..node (module.js:568:18)
at Object.module.(anonymous function) as .node
at Module.load (module.js:458:32)
at tryModuleLoad (module.js:417:12)
at Function.Module._load (module.js:409:3)
at Module.require (module.js:468:17)
at require (internal/module.js:20:19)
at Object. (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/wiring-pi/lib/exports.js:1:97)
Error: Module version mismatch. Expected 49, got 48.
at Error (native)
at process.module.(anonymous function) as dlopen
at Object.Module._extensions..node (module.js:568:18)
at Object.module.(anonymous function) as .node
at Module.load (module.js:458:32)
at tryModuleLoad (module.js:417:12)
at Function.Module._load (module.js:409:3)
at Module.require (module.js:468:17)
at require (internal/module.js:20:19)
at Object. (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/wiring-pi/lib/exports.js:1:97)

Unless I am reading this wrong this is expecting a Node module version that is not released yet?

I have followed all of your suggestions here even though that a downgrade to a previous version and not an upgrade to an unreleased version.. #2 #2
I have tried reinstalling electron, rebuilding it, removing the module folder and re cloning it. I’m at a loss.

The only other instance of this I could find is here don/node-eddystone-beacon#40 don/node-eddystone-beacon#40 Electron-rebuild seemed to work in their case. Not so much for me.

Источник

Error: Module version mismatch. Expected 46, got 14. #183

It seems that Aglio is not compatible with the latest node.js due its dependency lib protagonist and drafter are not compatible with the latest version of node.

Got this after upgrading node.js to 4.2.1

The text was updated successfully, but these errors were encountered:

@ye we are working on pushing a new release shortly that will support 3.x and 4.x. The fix (upgrading the nan library) is already complete, it is just waiting on a release.

@danielgtaylor thanks for the update!

Protagonist has pushed 1.1.1 which compiles on node 4. What’s the ETA for the next aglio release?

@artlogic I’m working on it today, just had to get Protagonist 1.1.1 out first to fix a bug! 😄

@danielgtaylor thanks for the update!

@ye, @artlogic version 2.2.0 is now released which supports Node.js 3.x and 4.x. Please note, it works with the new Protagonist, which itself is based on the new Drafter that does not yet generate JSON Schema from MSON and may contain some other MSON-related bugs. We are hard at work fixing them in upcoming backward-compatible releases!

@danielgtaylor thanks for all your hard work on this!

@danielgtaylor one more thing — where would I be able to find information about the timeline for supporting MSON in protagonist? Is there a list of blocking issues?

@danielgtaylor thank you! All works now.

@danielgtaylor one more thing — where would I be able to find information about the timeline for supporting MSON in protagonist? Is there a list of blocking issues

@artlogic Protagonist is a wrapper around the Drafter C++ library so you can look into there for a list of known issues.

We have a 2.0.0 milestone which shows all of the known issues we are working though. After that our intention is to work on JSON Schema support inside Drafter.

As for a timeline, we unfortunately don’t have any dates we can share at the moment. But these are the things we are working on.

@kylef thanks for taking the time to give a status update. I appreciate it.

Looks like node has just been updated to 5.0.0 yesterday. And yes, aglio is broken on the new version again. Sigh.

@ye I’ve been using Node.js 5.0.0 since yesterday with Aglio and it is working fine for me. I just had to reinstall Aglio because of the compiled dependencies (same issue everytime you switch major versions). What specifically is the problem you are seeing?

@danielgtaylor you are absolutely correct that unistall / reinstall worked! Thank you!

Using Node.js 5.0.0, uninstall/reinstall did not work for me. Still getting:
module.js:450
return process.dlopen(module, path._makeLong(filename));

@coderdave make sure you are uninstalling/installing in the right location (e.g. with -g for a global install) and make sure that npm and node are from the same install (e.g. mine are both in /usr/local/bin/. ). After that, let me know if it’s still an issue. Worst case you should be able to do a local install (without -g ) and run with ./node_modules/.bin/aglio to confirm it can work.

Reinstalling it globally seemed to work. Thanks.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

OS X: Error: Module version mismatch. Expected 48, got 49 #683

When trying to build for OS X getting the following error:
tsc && node-gyp rebuild && build —mac

Error: Module version mismatch. Expected 48, got 49.
at Error (native)
at Object.Module._extensions..node (module.js:583:18)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)
at Module.require (module.js:483:17)
at require (internal/module.js:20:19)
at Object. (/Users/Jenia/Desktop/git/electron-angular2-native/node_modules/macos-alias/lib/create.js:7:13)
at Module._compile (module.js:556:32)
at Object.Module._extensions..js (module.js:565:10)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)
at Module.require (module.js:483:17)
at require (internal/module.js:20:19)
at Object. (/Users/Jenia/Desktop/git/electron-angular2-native/node_modules/macos-alias/index.js:1:18)
at Module._compile (module.js:556:32)
at Object.Module._extensions..js (module.js:565:10)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)
at Module.require (module.js:483:17)
at require (internal/module.js:20:19)
at Object. (/Users/Jenia/Desktop/git/electron-angular2-native/node_modules/ds-store/index.js:2:13)
at Module._compile (module.js:556:32)
at Object.Module._extensions..js (module.js:565:10)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
From previous event:
at tsAwaiter (/Users/Jenia/Desktop/git/electron-angular2-native/node_modules/electron-builder/src/util/awaiter.ts:10:47)
at Object.build (/Users/Jenia/Desktop/git/electron-angular2-native/node_modules/electron-builder/src/builder.ts:195:52)
at Object. (/Users/Jenia/Desktop/git/electron-angular2-native/node_modules/electron-builder/src/build-cli.ts:27:28)
at Module._compile (module.js:556:32)
at Object.Module._extensions..js (module.js:565:10)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)
at Module.runMain (module.js:590:10)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:509:3

• Pull this repository: https://github.com/meltedspark/electron-angular2-native
• Run npm install
• Run npm run dist:osx

The text was updated successfully, but these errors were encountered:

Источник

«Module version mismatch» error #58

This is in the console, and it’s not starting the server because of it. Hopefully there’s enough info in the screenshot for versions — but please let me know if you need more.

The text was updated successfully, but these errors were encountered:

Seems you try to load native module bcrypt. Did you compiled the binaries against the current ironNode runtime version of node?

My help docs are a mess so here ‘s a link.

• iron-node —compile compile new binaries (not destructive) into a seperate subfolder.
• https://github.com/s-a/iron-node/blob/master/.iron-node.js#L8 native+ extends require to search native modules respecting the current v8 engine version. (compiled in the step before)

Sorry, need to check at the weekend!

On Fri, 9 Oct 2015 10:44 Stephan Ahlf notifications@github.com wrote:

—
Reply to this email directly or view it on GitHub
#58 (comment).

Hey, I tried today. Same problem. Here’s what I ran:

And I get the same error as above. I also tried with iron-node —compile but it just hung, so I figured it needed some pointing.

Hmm, do you have iron-node installed with npm? Or another package manager?
These Version DLL hell makes me crazy. I found this. Maybe it helps.
kelektiv/node.bcrypt.js#347 Other wise would be
cool if you could publish a reproducable sample. I d like to check this out
this weekend.

Did the compile process finished successfuly?
Am 12.10.2015 17:48 schrieb «Remy Sharp» notifications@github.com:

Hey, I tried today. Same problem. Here’s what I ran:

$ iron-node —compile=.
$ iron-node .

And I get the same error as above. I also tried with iron-node —compile
but it just hung, so I figured it needed some pointing.

—
Reply to this email directly or view it on GitHub
#58 (comment).

Seems like a npm update could fix it?

It was via npm (the version that comes with 4.1.0). Compilation did finish.

Just tried to reproduce but I fail in a step before on Windows32 with npm install bcrypt. 😞 I will retry frequently

@remy check this #60 (comment) out. I believe this can help you.

This works since iron-node 2.0.0

npm install bcrypt
iron-node —compile

In 2.0.2 I am getting this: Error: Module version mismatch. Expected 47, got 46.

node_modules/electron-prebuilt/dist/libgcrypt.so.11
Is this the suspect?
Why do you need it, in the first place?

I am not the creator of electron prebuilt, but have you recompiled binaries with electron —compile?

@s-a I’m having the same issue as @gritzko in 2.0.2.

In my case the only native module that I’m using is lwip. I’ve compiled lwip successfully using npm install with Node v4.2.2 and v5.1.1 (which I think the latest prebuilt version of Electron is using), so I don’t think it has any compatibility issues with Electron’s Node runtime.

I’ve tried iron-node —compile in multiple ways with no luck:

I also tried adding the .iron-node.js local config file with native+: true , but that didn’t seem to make any difference.

I always get this error:

Going forward, I’m really excited to see what happens with the external-node branch you just created. Since everyone is using a different version of Node, you might be able to prevent native module issues if iron-node was using the same version as the local version installed on the user’s machine.

Источник

Platform: Linux

При запуске моей программы node.js я получил следующую ошибку:

Error: Module version mismatch. Expected 11, got 1.

Ответ 1

вы можете указать ошибку:

Error: Module version mismatch. Expected 11, got 1.
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/home/user/node_modules/xml2json/node_modules/node-expat/lib/node-expat.js:4:13)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

а затем вы можете заметить ошибку в модуле или где-нибудь.

это потому, что вы обновили свой node, вы можете перестроить модуль, найденный выше.

i revole my question переустановить (удалить, затем установить) xml2json.

Удачи!

Ответ 2

npm rebuild также выполнит трюк

https://www.npmjs.org/doc/cli/npm-rebuild.html

Ответ 3

Platform: Linux

Для справок в будущем node.js v0.10.x (по крайней мере, v0.10.0) я получил эту ошибку:

Error: Module version mismatch. Expected 11, got 1.

Чтобы исправить это, я нашел эту интересную ссылку, а также получил некоторую помощь Бен Noordhuis. Следующая команда помогла мне избавиться от этой ошибки:

npm update

Ответ 4

Обычно это происходит, когда вы устанавливаете пакет с использованием одной версии Node, а затем меняете на другую версию. Это может произойти при обновлении Node или переключении на другую версию с помощью nvm.

Это также может произойти, если вы пытаетесь запустить процесс с правами root с установленным на глобальном уровне Node, но вы используете управляемый nvm node в своей учетной записи пользователя.

Чтобы исправить это, вы можете просто переустановить пакеты, используя правильную версию Node. Также убедитесь, что вы используете одну и ту же версию node для разных пользователей.

Ответ 5

Эта проблема возникает из-за следующего сценария: вы используете Node, например, версию 5. Вы добавляете в свой проект несколько библиотек, создаете и запускаете их. Все ваши библиотеки будут скомпилированы в Node версии 5.

И затем вы обновите свой Node, например, до версии 6. И затем вы запустите несколько команд, которые используют node, например npm run test. Проблема здесь: вы используете более новую версию Node для запуска библиотек, скомпилированных более старыми node.

Решение этой задачи выполняется двумя следующими командами:

rm -rf node_modules // force remove node_modules directory
npm install         // install again all libraries. 

Ответ 6

Еще одна вещь, которую нужно попробовать, если вы используете nvm — убедитесь, что вы используете ту же версию node как в глобальном, так и в приложении.

:/$ node -v
v6.0.0

:/var/www/app$ node -v
v6.2.0

Если они не согласны:

:/$ nvm use 6.2.0
Now using node v6.2.0 (npm v3.8.9)

(Это то, что сработало для меня.)

Ответ 7

Вы можете найти список версий модулей node и их соответствующую версию node на этой странице https://nodejs.org/en/download/releases/

NODE_MODULE_VERSION ссылается на номер версии ABI (прикладной двоичный интерфейс) Node.js, используемый для определения того, какие версии Node.js скомпилированных исполняемых бинарных файлов С++ могут быть загружены без необходимости повторного использования, скомпилирован. Раньше оно хранилось как шестнадцатеричное значение в более ранних версиях, но теперь оно представлено как целое число.

Ответ 8

Иногда проблема возникает из-за версии nodejs.

Попробуйте обновить версию npm и nodejs.
Следуйте этой ссылке, чтобы обновить ваши узлы.

И обновить использование npm:

sudo npm install npm -g

Надеюсь, это поможет!

Ответ 9

В моем случае причиной ошибки был С++ — AddOn, который был скомпилирован с другой версией node.js.

Так что вам, возможно, придется перекомпилировать свой С++-AddOn, поэтому основные версии аддона и node.js будут выполняться.

Ответ 10

У меня была эта проблема с systemd, но я мог запустить приложение, используя node myapp.js.

Оказывается, что путь в ExecStart отличался от пути, который я получил от which node. Изменение этого в файле службы исправило это для меня.

источник

Ответ 11

Ни один из ответов не работал у меня, так что вот мое решение.

Error: Module version mismatch. Expected 48, got 51.
at Error (native)
at Object.Module._extensions..node (module.js:597:18)

48 и 51 соответствуют версиям node, найденным на странице выпуска nodejs:
https://nodejs.org/en/download/releases/

Итак, я установил nvm, диспетчер версий node и переключил мою версию node на 48 (6.11.x), а затем запустил
rm -rf node_modules/
а также
npm install

Мой конкретный модуль, mcrypt, зависит от двоичных файлов С++, а версия модуля node имеет прямое влияние:

NODE_MODULE_VERSION ссылается на номер версии ABI (прикладной двоичный интерфейс) Node.js, используемый для определения того, какие версии Node.js скомпилированных исполняемых бинарных файлов С++ могут быть загружены без необходимости повторного использования, скомпилирован. Раньше оно хранилось как шестнадцатеричное значение в более ранних версиях, но теперь оно представлено как целое число.

Ответ 12

Самый простой способ попасть туда, где вам нужно, после того, как вы изменили версию своего узла, это:

rm -Rf node_modules/&& yarn && yarn start

Замените yarn start любой командой, которая необходима для запуска сервера.

Ответ 13

Если модуль является надстройкой c++, вам, возможно, придется пересобрать node-gyp

node-gyp rebuild

Ответ 14

Ни один из приведенных выше ответов не решил проблему для меня. Решением для меня было использование xml2js вместо xml2json.