'node-gyp rebuild' fails when attempting to rebuild latex

[ExecutorElassus]

latex 0.5.0 apparently contains native modules that were compiled for an earlier version of Atom than mine (1.29.0-beta2), but rebuild fails with the following (this is the partial log from atom's internal console output):

/usr/share/atom/resources/app/apm/node_modules/npm/bin/node-gyp-bin/node-gyp: line 5: /usr/share/atom/resources/app/apm/bin/../node_modules/.bin/node-gyp: Permission denied

npm ERR! Linux 4.17.11-gentoo
npm ERR! argv "/usr/share/atom/resources/app/apm/bin/node" "/usr/share/atom/resources/app/apm/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/[$HOME]/.atom/.apm/.apmrc" "--userconfig" "/[$HOME]/.atom/.apmrc" "rebuild" "--runtime=electron" "--target=2.0.5" "--arch=x64"
npm ERR! node v6.9.5
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! abstract-socket@2.0.0 install: `node-gyp rebuild`
npm ERR! Exit status 126
npm ERR! 
npm ERR! Failed at the abstract-socket@2.0.0 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the abstract-socket package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs abstract-socket
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls abstract-socket
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /[$HOME]/.atom/packages/latex/npm-debug.log

That first line suggests something's wrong with my permissions, but I'm not sure how to debug.

Thanks for the help.

[saghul]

Sorry, I have no idea how that is related to this plugin.

[ExecutorElassus]

well, according to the error report, the failure is with the node-gyp rebuild command, which it claims belongs to this plugin, and that I should tell you that that command is failing. Does node-gyp not belong to the abstract-socket plugin?

[saghul]

No, it does not. It's used to build other packages which have native code in them, such as this plugin. I think you are running into this because of some mismatch in running / built Node (or Atom) version.

[ExecutorElassus]

ah. In that case, I'm going to assume that it's probably something lacking in my local node.js installation, since the atom package is relatively new.

Cheers.