Upgrading from node 8 to node 10: error regarding “module compiled against a different Node.js version”
3
I am now getting the following error when I run my node app. It has only occurred after I upgraded from node 8.12.0 to node 10.13.0 (which is now "recommended for most users"). The problem seems to relate to node-expat, which I don't use directly but which is a dependency of xml2json (which I do use directly).
/root/workspace/myapp/node_modules/bindings/bindings.js:88
throw e
^
Error: The module '/root/workspace/myapp/node_modules/node-expat/build/Release/node_expat.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 64. This version of Node.js requires
NODE_MODULE_VERSION 57. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
at Object.Module._extensions..node (module.js:682:18)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at bindings (/root/workspace/myapp/node_modules/bindings/bindings.js:81:44)
at Object.<anonymous> (/root/workspace/myapp/node_modules/node-expat/lib/node-expat.js:4:32)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
What do I need to do to fix this? Yes, I have completely removed node_modules and done npm install as per this thread... doesn't help.
node.js
asked Nov 13 '18 at 16:31
drmrbrewerdrmrbrewer
1,99662684
|
show 4 more comments
3
I am now getting the following error when I run my node app. It has only occurred after I upgraded from node 8.12.0 to node 10.13.0 (which is now "recommended for most users"). The problem seems to relate to node-expat, which I don't use directly but which is a dependency of xml2json (which I do use directly).
/root/workspace/myapp/node_modules/bindings/bindings.js:88
throw e
^
Error: The module '/root/workspace/myapp/node_modules/node-expat/build/Release/node_expat.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 64. This version of Node.js requires
NODE_MODULE_VERSION 57. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
at Object.Module._extensions..node (module.js:682:18)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at bindings (/root/workspace/myapp/node_modules/bindings/bindings.js:81:44)
at Object.<anonymous> (/root/workspace/myapp/node_modules/node-expat/lib/node-expat.js:4:32)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
What do I need to do to fix this? Yes, I have completely removed node_modules and done npm install as per this thread... doesn't help.
node.js
asked Nov 13 '18 at 16:31
drmrbrewerdrmrbrewer
1,99662684
1
Try to also deletepackage-lock.json
– Gabriel Bleu
Nov 13 '18 at 16:35
@GabrielBleu there is nopackage-lock.json
– drmrbrewer
Nov 13 '18 at 16:59
Did you trynpm cache clean -f(and reinstall everything)? There were multiple issues with npm registry in recent weeks. See the incident reports.
– lependu
Nov 13 '18 at 17:02
I wonder whether it has something to do with this commit made 3 months ago tonode-expat: github.com/astro/node-expat/commit/…. Thexml2jsonpackage is still referencing version2.3.16ofnode-expatin itspackage-lock.json(see github.com/buglabs/node-xml2json/blob/master/package-lock.json).
– drmrbrewer
Nov 13 '18 at 17:06
@lependu that doesn't help either. Re my comment just above... could it be that? How do I force a different version ofnode-expatonxml2jsonwhenxml2jsonisn't my own module... I'm justrequireing that as a dependency in my node app (andpackage.json)?
– drmrbrewer
Nov 13 '18 at 17:10
|
show 4 more comments
3
3
3
I am now getting the following error when I run my node app. It has only occurred after I upgraded from node 8.12.0 to node 10.13.0 (which is now "recommended for most users"). The problem seems to relate to node-expat, which I don't use directly but which is a dependency of xml2json (which I do use directly).
/root/workspace/myapp/node_modules/bindings/bindings.js:88
throw e
^
Error: The module '/root/workspace/myapp/node_modules/node-expat/build/Release/node_expat.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 64. This version of Node.js requires
NODE_MODULE_VERSION 57. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
at Object.Module._extensions..node (module.js:682:18)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at bindings (/root/workspace/myapp/node_modules/bindings/bindings.js:81:44)
at Object.<anonymous> (/root/workspace/myapp/node_modules/node-expat/lib/node-expat.js:4:32)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
What do I need to do to fix this? Yes, I have completely removed node_modules and done npm install as per this thread... doesn't help.
node.js
asked Nov 13 '18 at 16:31
drmrbrewerdrmrbrewer
1,99662684
I am now getting the following error when I run my node app. It has only occurred after I upgraded from node 8.12.0 to node 10.13.0 (which is now "recommended for most users"). The problem seems to relate to node-expat, which I don't use directly but which is a dependency of xml2json (which I do use directly).
/root/workspace/myapp/node_modules/bindings/bindings.js:88
throw e
^
Error: The module '/root/workspace/myapp/node_modules/node-expat/build/Release/node_expat.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 64. This version of Node.js requires
NODE_MODULE_VERSION 57. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
at Object.Module._extensions..node (module.js:682:18)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at bindings (/root/workspace/myapp/node_modules/bindings/bindings.js:81:44)
at Object.<anonymous> (/root/workspace/myapp/node_modules/node-expat/lib/node-expat.js:4:32)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
What do I need to do to fix this? Yes, I have completely removed node_modules and done npm install as per this thread... doesn't help.
node.js
node.js
asked Nov 13 '18 at 16:31
drmrbrewerdrmrbrewer
1,99662684
asked Nov 13 '18 at 16:31
drmrbrewerdrmrbrewer
1,99662684
asked Nov 13 '18 at 16:31
drmrbrewerdrmrbrewer
1,99662684
asked Nov 13 '18 at 16:31
drmrbrewerdrmrbrewer
1,99662684
asked Nov 13 '18 at 16:31
drmrbrewerdrmrbrewer
1,99662684
1,99662684
1
Try to also deletepackage-lock.json
– Gabriel Bleu
Nov 13 '18 at 16:35
@GabrielBleu there is nopackage-lock.json
– drmrbrewer
Nov 13 '18 at 16:59
Did you trynpm cache clean -f(and reinstall everything)? There were multiple issues with npm registry in recent weeks. See the incident reports.
– lependu
Nov 13 '18 at 17:02
I wonder whether it has something to do with this commit made 3 months ago tonode-expat: github.com/astro/node-expat/commit/…. Thexml2jsonpackage is still referencing version2.3.16ofnode-expatin itspackage-lock.json(see github.com/buglabs/node-xml2json/blob/master/package-lock.json).
– drmrbrewer
Nov 13 '18 at 17:06
@lependu that doesn't help either. Re my comment just above... could it be that? How do I force a different version ofnode-expatonxml2jsonwhenxml2jsonisn't my own module... I'm justrequireing that as a dependency in my node app (andpackage.json)?
– drmrbrewer
Nov 13 '18 at 17:10
|
show 4 more comments
1
Try to also deletepackage-lock.json
– Gabriel Bleu
Nov 13 '18 at 16:35
@GabrielBleu there is nopackage-lock.json
– drmrbrewer
Nov 13 '18 at 16:59
Did you trynpm cache clean -f(and reinstall everything)? There were multiple issues with npm registry in recent weeks. See the incident reports.
– lependu
Nov 13 '18 at 17:02
I wonder whether it has something to do with this commit made 3 months ago tonode-expat: github.com/astro/node-expat/commit/…. Thexml2jsonpackage is still referencing version2.3.16ofnode-expatin itspackage-lock.json(see github.com/buglabs/node-xml2json/blob/master/package-lock.json).
– drmrbrewer
Nov 13 '18 at 17:06
@lependu that doesn't help either. Re my comment just above... could it be that? How do I force a different version ofnode-expatonxml2jsonwhenxml2jsonisn't my own module... I'm justrequireing that as a dependency in my node app (andpackage.json)?
– drmrbrewer
Nov 13 '18 at 17:10
1
1
Try to also delete
package-lock.json– Gabriel Bleu
Nov 13 '18 at 16:35
Try to also delete
package-lock.json– Gabriel Bleu
Nov 13 '18 at 16:35
@GabrielBleu there is no
package-lock.json– drmrbrewer
Nov 13 '18 at 16:59
@GabrielBleu there is no
package-lock.json– drmrbrewer
Nov 13 '18 at 16:59
Did you try
npm cache clean -f (and reinstall everything)? There were multiple issues with npm registry in recent weeks. See the incident reports.– lependu
Nov 13 '18 at 17:02
Did you try
npm cache clean -f (and reinstall everything)? There were multiple issues with npm registry in recent weeks. See the incident reports.– lependu
Nov 13 '18 at 17:02
I wonder whether it has something to do with this commit made 3 months ago to
node-expat: github.com/astro/node-expat/commit/…. The xml2json package is still referencing version 2.3.16 of node-expat in its package-lock.json (see github.com/buglabs/node-xml2json/blob/master/package-lock.json).– drmrbrewer
Nov 13 '18 at 17:06
I wonder whether it has something to do with this commit made 3 months ago to
node-expat: github.com/astro/node-expat/commit/…. The xml2json package is still referencing version 2.3.16 of node-expat in its package-lock.json (see github.com/buglabs/node-xml2json/blob/master/package-lock.json).– drmrbrewer
Nov 13 '18 at 17:06
@lependu that doesn't help either. Re my comment just above... could it be that? How do I force a different version of
node-expat on xml2json when xml2json isn't my own module... I'm just requireing that as a dependency in my node app (and package.json)?– drmrbrewer
Nov 13 '18 at 17:10
@lependu that doesn't help either. Re my comment just above... could it be that? How do I force a different version of
node-expat on xml2json when xml2json isn't my own module... I'm just requireing that as a dependency in my node app (and package.json)?– drmrbrewer
Nov 13 '18 at 17:10
|
show 4 more comments
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53285484%2fupgrading-from-node-8-to-node-10-error-regarding-module-compiled-against-a-dif%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53285484%2fupgrading-from-node-8-to-node-10-error-regarding-module-compiled-against-a-dif%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Try to also delete
package-lock.json– Gabriel Bleu
Nov 13 '18 at 16:35
@GabrielBleu there is no
package-lock.json– drmrbrewer
Nov 13 '18 at 16:59
Did you try
npm cache clean -f(and reinstall everything)? There were multiple issues with npm registry in recent weeks. See the incident reports.– lependu
Nov 13 '18 at 17:02
I wonder whether it has something to do with this commit made 3 months ago to
node-expat: github.com/astro/node-expat/commit/…. Thexml2jsonpackage is still referencing version2.3.16ofnode-expatin itspackage-lock.json(see github.com/buglabs/node-xml2json/blob/master/package-lock.json).– drmrbrewer
Nov 13 '18 at 17:06
@lependu that doesn't help either. Re my comment just above... could it be that? How do I force a different version of
node-expatonxml2jsonwhenxml2jsonisn't my own module... I'm justrequireing that as a dependency in my node app (andpackage.json)?– drmrbrewer
Nov 13 '18 at 17:10