search

y-takey / atom-mermaid

Preview mermaid on atom editor
MIT License
42 stars 7 forks source link

package could not be loaded because they contain native modules that aren't compatible with this version of Atom #5

Closed despairblue closed 8 years ago

despairblue commented 9 years ago

I'm getting this on linux, though not on mac os

Listed below are the incompatible native modules that this package depends on.

contextify@0.1.14
Error message: Module did not self-register.

screenshot from 2015-07-25 03-12-00

Versions

y-takey commented 9 years ago

@despairblue Hi, I think that the problem has occurred due old version of node.js . Are you able to version up of your node.js? Please try to re-install the package, if you are able to.

despairblue commented 9 years ago

I actually installed iojs 1.5.1 (the one mentioned) reissued npm install in the project folder, but to no avail.

y-takey commented 9 years ago

Sorry, the latest version of iojs seems to 2.4. Your iojs it looks like old.

despairblue commented 9 years ago

Yeah, because I used the one that atom (see screenshot above) uses :smile:

Atom does not use the system version of node, iojs or npm, it bundles everything, so there is no reason to use another version. If I'd compile it with 2.4 and atom tries to load it with 1.5.1, what's the point? :smiley:

despairblue commented 9 years ago

Just to be sure, I did it again with 2.4. Same result.

y-takey commented 9 years ago

Hmm, Please check atom environment, node path is contained process.env.PATH. ( Open atom menu [View → Developer → Toggle Developer Tools], and exec process.env.PATH on console ) If node path is not contained, add the following line to your init.coffe. ( Open atom menu [Atom → Open Your Init Script )

process.env.PATH = ["/to/your/node/path", process.env.PATH].join(":")

e.g. path is "/Users/xxx/.nvm/v0.12.7/bin"

Sorry for not familiar with atom editor and node.js .

despairblue commented 9 years ago

Sorry, I didn't mean to sound harsh. :smiley:

The path contains /usr/bin/local, which is where my node binary resides. I'm not convinced that this is the problem.

I'll come back to this issue when I've got more spare time to debug this. Please keep it open.

Cheers!

y-takey commented 9 years ago

Roger!

jhartma commented 8 years ago

I have the exact same problem. I am on node 4.0.0 and atom 1.0.11. Atom also knows the node path.

y-takey commented 8 years ago

Hi, @jhartma

Do you also uses the linux?

jhartma commented 8 years ago

yep, I'm on Arch Linux

jhartma commented 8 years ago

Actually I think it comes down to the contextify module used by mermaid which doesnt compile, and it's not something atom-package related

despairblue commented 8 years ago

I also tried apm rebuild. It finishes without any errors, but loading contextify still bails.

y-takey commented 8 years ago

Thanks,

contextify seems to be a problem, but it seems to have been left... https://github.com/atom/atom/issues/8175

despairblue commented 8 years ago

fixed with atom 1.0.12

y-takey commented 8 years ago

Thank you so much!

despairblue commented 8 years ago

Thanks to you for making this package and to the atom folks for upgrading to a more recent iojs version :smiley: