“serialport” node module version error message confusing
2
Does the following node error mean I need to upgrade the serialport module, or downgrade nodejs, or something else? (It used to work until I updated ubuntu from 16.04 to 18.04)
Error: The module '../node_modules/@serialport/bindings/build/Release/bindings.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 67. 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`).
I have tried:
rm package-lock.json;
rm -rf node_modules;
npm install
npm rebuild
npm install serialport --build-from-source
sudo npm install serialport --unsafe-perm --build-from-source
Is there a simple way to fix this?
node.js
asked Nov 23 '18 at 20:21
DrBubblesDrBubbles
1536
add a comment |
2
Does the following node error mean I need to upgrade the serialport module, or downgrade nodejs, or something else? (It used to work until I updated ubuntu from 16.04 to 18.04)
Error: The module '../node_modules/@serialport/bindings/build/Release/bindings.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 67. 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`).
I have tried:
rm package-lock.json;
rm -rf node_modules;
npm install
npm rebuild
npm install serialport --build-from-source
sudo npm install serialport --unsafe-perm --build-from-source
Is there a simple way to fix this?
node.js
asked Nov 23 '18 at 20:21
DrBubblesDrBubbles
1536
add a comment |
2
2
2
Does the following node error mean I need to upgrade the serialport module, or downgrade nodejs, or something else? (It used to work until I updated ubuntu from 16.04 to 18.04)
Error: The module '../node_modules/@serialport/bindings/build/Release/bindings.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 67. 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`).
I have tried:
rm package-lock.json;
rm -rf node_modules;
npm install
npm rebuild
npm install serialport --build-from-source
sudo npm install serialport --unsafe-perm --build-from-source
Is there a simple way to fix this?
node.js
asked Nov 23 '18 at 20:21
DrBubblesDrBubbles
1536
Does the following node error mean I need to upgrade the serialport module, or downgrade nodejs, or something else? (It used to work until I updated ubuntu from 16.04 to 18.04)
Error: The module '../node_modules/@serialport/bindings/build/Release/bindings.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 67. 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`).
I have tried:
rm package-lock.json;
rm -rf node_modules;
npm install
npm rebuild
npm install serialport --build-from-source
sudo npm install serialport --unsafe-perm --build-from-source
Is there a simple way to fix this?
node.js
node.js
asked Nov 23 '18 at 20:21
DrBubblesDrBubbles
1536
asked Nov 23 '18 at 20:21
DrBubblesDrBubbles
1536
edited Nov 23 '18 at 20:46
DrBubbles
asked Nov 23 '18 at 20:21
DrBubblesDrBubbles
1536
asked Nov 23 '18 at 20:21
DrBubblesDrBubbles
1536
asked Nov 23 '18 at 20:21
DrBubblesDrBubbles
1536
1536
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
1
Completely removed nodejs npm, reinstalled, ran nodejs main.js and then installed packages as necessary using npm. Works now.
answered Nov 23 '18 at 21:59
DrBubblesDrBubbles
1536
npm rebuildshould have taken care of it. Sounds like something got stuck somehow. Was your module installed globally by chance?
– Brad
Nov 23 '18 at 22:50
Possibly, I think I had at some point installed node with sudo in a different location at some point in the past, and it was hanging on to those definitions. I searched and removed any instances I could find and then reinstalled and that solved it. Thanks.
– DrBubbles
Nov 23 '18 at 23:12
add a comment |
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%2f53452548%2fserialport-node-module-version-error-message-confusing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
Completely removed nodejs npm, reinstalled, ran nodejs main.js and then installed packages as necessary using npm. Works now.
answered Nov 23 '18 at 21:59
DrBubblesDrBubbles
1536
npm rebuildshould have taken care of it. Sounds like something got stuck somehow. Was your module installed globally by chance?
– Brad
Nov 23 '18 at 22:50
Possibly, I think I had at some point installed node with sudo in a different location at some point in the past, and it was hanging on to those definitions. I searched and removed any instances I could find and then reinstalled and that solved it. Thanks.
– DrBubbles
Nov 23 '18 at 23:12
add a comment |
1
Completely removed nodejs npm, reinstalled, ran nodejs main.js and then installed packages as necessary using npm. Works now.
answered Nov 23 '18 at 21:59
DrBubblesDrBubbles
1536
npm rebuildshould have taken care of it. Sounds like something got stuck somehow. Was your module installed globally by chance?
– Brad
Nov 23 '18 at 22:50
Possibly, I think I had at some point installed node with sudo in a different location at some point in the past, and it was hanging on to those definitions. I searched and removed any instances I could find and then reinstalled and that solved it. Thanks.
– DrBubbles
Nov 23 '18 at 23:12
add a comment |
1
1
1
Completely removed nodejs npm, reinstalled, ran nodejs main.js and then installed packages as necessary using npm. Works now.
answered Nov 23 '18 at 21:59
DrBubblesDrBubbles
1536
Completely removed nodejs npm, reinstalled, ran nodejs main.js and then installed packages as necessary using npm. Works now.
answered Nov 23 '18 at 21:59
DrBubblesDrBubbles
1536
answered Nov 23 '18 at 21:59
DrBubblesDrBubbles
1536
answered Nov 23 '18 at 21:59
DrBubblesDrBubbles
1536
answered Nov 23 '18 at 21:59
DrBubblesDrBubbles
1536
1536
npm rebuildshould have taken care of it. Sounds like something got stuck somehow. Was your module installed globally by chance?
– Brad
Nov 23 '18 at 22:50
Possibly, I think I had at some point installed node with sudo in a different location at some point in the past, and it was hanging on to those definitions. I searched and removed any instances I could find and then reinstalled and that solved it. Thanks.
– DrBubbles
Nov 23 '18 at 23:12
add a comment |
npm rebuildshould have taken care of it. Sounds like something got stuck somehow. Was your module installed globally by chance?
– Brad
Nov 23 '18 at 22:50
Possibly, I think I had at some point installed node with sudo in a different location at some point in the past, and it was hanging on to those definitions. I searched and removed any instances I could find and then reinstalled and that solved it. Thanks.
– DrBubbles
Nov 23 '18 at 23:12
npm rebuild should have taken care of it. Sounds like something got stuck somehow. Was your module installed globally by chance?– Brad
Nov 23 '18 at 22:50
npm rebuild should have taken care of it. Sounds like something got stuck somehow. Was your module installed globally by chance?– Brad
Nov 23 '18 at 22:50
Possibly, I think I had at some point installed node with sudo in a different location at some point in the past, and it was hanging on to those definitions. I searched and removed any instances I could find and then reinstalled and that solved it. Thanks.
– DrBubbles
Nov 23 '18 at 23:12
Possibly, I think I had at some point installed node with sudo in a different location at some point in the past, and it was hanging on to those definitions. I searched and removed any instances I could find and then reinstalled and that solved it. Thanks.
– DrBubbles
Nov 23 '18 at 23:12
add a comment |
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%2f53452548%2fserialport-node-module-version-error-message-confusing%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
