asyncawait require-ing a higher fibers than exist? about asyncawait HOT 7 CLOSED

Hi @vanchisel,

Are you still having this problem?

If you've recently updated your node version, then any native modules (such as node-fibers) previously installed in node_modules may stop working due to new Node API incompatibilities. The usual solution is to delete the node_modules directory entirely, then do npm install again. Does that work for you?

from asyncawait.

Hello @yortus,

Thank you for responding. I deleted node_modules just now and it didn't work: ...win32-ia32-v8-5.1\fibers.node is missing. The problem seems with building 'node fibers'. I'd love to use asyncawait. I abandoned nwjs for electron because nw-gyp couldn't build node sqlite3+ other issues. Electron only has problem with asyncawait/fibers.

Right now I'm using Bluebird but would love another help because I can see some Promise.then() aren't flowing correctly.

from asyncawait.

Hi, I am having a similar issue and am also using electron,
get a "node_modules\fibers\bin\win32-x64-v8-5.2\fibers.node" is missing error message.
npm installing fibers only gives up to win32-x64-v8-5.0

from asyncawait.

I don't know much about electron but I found this page in the Electron docs. Could it be relevant?

from asyncawait.

Hi, I am also now running into this issue while using electron.

I tried that link you referred to @yortus but still no luck and I'm running out of ideas.

Any other ideas? Thanks

from asyncawait.

Similar Issue confirmed on part as well:

Error: /home/xxxx/xxxxxxxxx/server/node_modules/fibers/bin/linux-x64-v8-5.1/fibers.node is missing. Try reinstalling node-fibers?

Issue is most likely on the part of node-fibers, atleast in my case, as i can't seem to install it on its own due to build errors on Arch Linux 64.

from asyncawait.

Since this problem isn't caused by or solvable by asyncawait, I'm going to close this. The fibers repo may be a more useful place to further discuss this. Note there are several issues there about this already. Unfortunately it seems to be a not-supported scenario.

from asyncawait.