Incompatible native modules that this package depends on. about nvatom

[seongjaelee]

This is an error that had been bugging me for a week. Hmmm...

Did you just install the package from Atom? Or did you git clone-ed the repository and apm build-ed it? If the later, try to delete node_modules and run apm build and apm rebuild. In the error message box from Atom, there is some button like "reload atom" within the message box. When I clicked it after callling apm build/rebuild, it was gone.

If it's still not working, which OSX are you using? Are you using the most recent atom version (1.0.11)?

[jonmagic]

I'm asking for help in the Atom chat room on Slack and if that doesn't pan out I'm going to ping one of the Atom devs directly for help (I just so happen to work with them at GitHub 😁).

[seongjaelee]

Thanks very much Jonathan! 😄

To clarify, I don't experience the problem anymore. Mine was #24. It happend mostly during apm test, but when I was playing with npm and apm, sometimes I got the error even on the atom editor. But it got easily removed from atom editor when I rebuilt the package only using apm.

I'll be waiting for replies from lexicalunit.

[lexicalunit]

I'm running OS X 10.10.4, also I'm using the latest Atom version:

$ atom --version
1.0.11

@seongjaelee I tried repo cloning first, then the apm install method second. I opened the ticket after I saw the issue come up from the apm install method.

apm build is an invalid command:

$ apm build
Unrecognized command: build

Did you mean npm install? Here's my log from running that command (after cloning the repo into ~/.atom/packages):

> npm install
|
> [email protected] install /Users/atroschinetz/.atom/packages/nvatom/node_modules/chokidar/node_modules/fsevents
> node-gyp rebuild

  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node
[email protected] node_modules/underscore-plus
└── [email protected]

[email protected] node_modules/fs-plus
├── [email protected]
├── [email protected]
└── [email protected]

[email protected] node_modules/docquery
├── [email protected]
├── [email protected]
├── [email protected] ([email protected])
└── [email protected]

[email protected] node_modules/atom-space-pen-views
├── [email protected]
└── [email protected] ([email protected], [email protected])

[email protected] node_modules/chokidar
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected], [email protected])
├── [email protected] ([email protected])
└── [email protected] ([email protected])

This results in the error I reported. I was also able to run apm rebuild, here's the log:

$ apm rebuild
Rebuilding modules ✓

After doing that I still see the incompatibility error.

[seongjaelee]

@lexicalunit Yes, it is apm install, as you said. I thought mixing apm and npm is the problem, 'cause for my case, apm's npm version and npm's version didn't match.

So, did you just install the package from Atom, not cloning the git repository? If so, you don't have to run apm/npm commands at all from the beginning.

[jonmagic]

Today I updated Atom to 1.0.12 and after that my local development copy of nvatom stopped working with the fsevent module version mismatch error. It recommended I rebuild so I tried that but it failed.

I then uninstalled my local development copy of the nvatom package and reinstalled the package from the Install section in Settings and it works perfectly now. I haven't been able to reproduce the issue since then.

[seongjaelee]

I am in the same situation. When I click the red bug icon on the bottom right, it shows the following error messages.

nvatom 0.8.1.

/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/bin/node-gyp-bin/node-gyp: line 3: node: command not found

npm ERR! Darwin 14.5.0
npm ERR! argv "/Applications/Atom.app/Contents/Resources/app/apm/bin/node" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/Users/seongjae/.atom/.apm/.apmrc" "--userconfig" "/Users/seongjae/.atom/.apmrc" "rebuild" "--target=0.30.6" "--arch=x64"
npm ERR! node v0.10.40
npm ERR! npm  v2.13.3
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the [email protected] install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the fsevents 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 their info via:
npm ERR!     npm owner ls fsevents
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/seongjae/github/notational-velocity/npm-debug.log

There is a "Rebuild Packages" button on the top right, but when I click it, it gives me a "Rebuild Failed" message.

[seongjaelee]

seongjae:notational-velocity apm install; apm rebuild; apm test;
Installing modules ✓
Rebuilding modules ✓
[85686:0917/204132:INFO:renderer_main.cc(200)] Renderer process started
[85682:0917/204132:INFO:CONSOLE(46)] "Window load time: 330ms", source: file:///Applications/Atom.app/Contents/Resources/app.asar/static/index.js (46)
[85682:0917/204133:INFO:CONSOLE(755)] "Failed to require the main module of 'nvatom' because it requires an incompatible native module.
Run `apm rebuild` in the package directory to resolve.", source: /Applications/Atom.app/Contents/Resources/app.asar/src/package.js (755)
F[85682:0917/204133:INFO:CONSOLE(755)] "Failed to require the main module of 'nvatom' because it requires an incompatible native module.
Run `apm rebuild` in the package directory to resolve.", source: /Applications/Atom.app/Contents/Resources/app.asar/src/package.js (755)
F

nvAtom
  when the nvatom:toggle event is triggered
    it attaches and then detaches the view
      Expected null to exist.
        at [object Object].<anonymous> (/Users/seongjae/github/notational-velocity/spec/notational-velocity-spec.coffee:27:59)
        at _fulfilled (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/q/q.js:794:54)
        at self.promiseDispatch.done (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/q/q.js:823:30)
        at Promise.promise.promiseDispatch (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/q/q.js:756:13)
        at /Applications/Atom.app/Contents/Resources/app.asar/node_modules/q/q.js:564:44
        at flush (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/q/q.js:110:17)
        at doNTCallback0 (node.js:416:9)
        at process._tickCallback (node.js:345:13)
    it checks if we banned the default directory under packages directory
      TypeError: Cannot read property 'querySelector' of null
        at [object Object].<anonymous> (/Users/seongjae/github/notational-velocity/spec/notational-velocity-spec.coffee:48:47)
        at _fulfilled (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/q/q.js:794:54)
        at self.promiseDispatch.done (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/q/q.js:823:30)
        at Promise.promise.promiseDispatch (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/q/q.js:756:13)
        at /Applications/Atom.app/Contents/Resources/app.asar/node_modules/q/q.js:564:44
        at flush (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/q/q.js:110:17)
        at doNTCallback0 (node.js:416:9)
        at process._tickCallback (node.js:345:13)


Finished in 0.182 seconds
2 tests, 3 assertions, 2 failures, 0 skipped

Tests failed

[seongjaelee]

Hmm, I re-run the travis test, but it passes, even with atom 1.0.13. I guess there must be some cache hidden somewhere outside node_modules.
https://travis-ci.org/seongjaelee/nvatom/builds/80760310

[seongjaelee]

Hmm, I deleted .atom/.apm, .atom/.node_gyp, .atom/compile-cache, .atom/storage, nvatom/node_modules but it still gives the same problem.

[seongjaelee]

I deleted my nvatom from .atom/packages, installed it again. It still gave the red bug icon on the bottom right.
I rebuilded it by using the botton on the top right, and then reloaded atom, and then the error is gone.

[seongjaelee]

@lexicalunit, do you still have the problem? If I don't hear from you for a week, I'll close this issue "not reproducible". You can try delete-install-rebuild-reload as described above... I cannot reproduce it again, but it seems like it is related to some cache outside of the package.

[lexicalunit]

Weird. Installing from the Settings panel within Atom seems to work fine.

It's just installing manually from git or installing using apm that seems to have issues for me.

[lexicalunit]

Actually, I just got it to work installing manually from git. 👍