search

jperkin / node-rpio

Raspberry Pi GPIO library for node.js
856 stars 123 forks source link

Node version error after init with option: gpiomem false #137

Closed ralflici closed 2 years ago

ralflici commented 3 years ago

This is the code I'm trying to run on the Raspberry Pi: 

let options = {
        gpiomem: false,
        mapping: 'physical',
        mock: undefined,
        close_on_exit: true,
}

const rpio = require("rpio");
rpio.init(options);

and the error I get from node when trying to run the script (with sudo):

<path>/node_modules/bindings/bindings.js:121
        throw e;
        ^

Error: The module '<path>/node_modules/rpio/build/Release/rpio.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 83. This version of Node.js requires
NODE_MODULE_VERSION 64. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:807:18)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at bindings (<path>/node_modules/bindings/bindings.js:112:48)
    at Object.<anonymous> (<path>/node_modules/rpio/lib/rpio.js:17:34)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)

I'v tried npm rebuild and npm install, I have also deleted manually the node_modules folder and reinstalled the rpio library but it did not solve my problem.
Scripts that handle GPIO functions show no problems but now I'm interested in PWM so the the gpiomem falg must be set to false in my case.

Hardware: Raspberry PI 3 Model B+
Node: v14.15.4
NPM: v6.14.10

jperkin commented 3 years ago

It's likely that the version of node used when you sudo is different to the one you get as a regular user.

You should be able to verify this by comparing the output of these two commands:

$ node --version

$ sudo node --version

In your case the node run without sudo, and therefore the one used by npm install, is newer than the second.

By default the $PATH environment variable is not passed to the sudo environment. You can either fix this in sudoers by adding it to the list of variables that are passed through, or be specific about which node you want to run on the command line, e.g.:

$ sudo /path/to/newer/node ...

Hope that helps.

ralflici commented 3 years ago

Yes you were right, the node version of sudo was outdated and different from the "regular" one. I just edited the sudoers file by prepending the path to the new version of node in the secure_path variable. Now the script is running without problems.
Thank you very much!