Cannot find module "fibers/future", on Win7

Hi everyone !

Today I got an error message on my project telling me it couldn’t find the fibers module. So, thinking I maybe messed up somewhere, I created a new project and then I builded it :

meteor create testProject

And there it was ! The same error again. So I thought maybe I should install the missing module.

meteor npm install --save fibers

I re run and then the same error occur but with the “source-map-support” module. So I install it and try again …
Spoiler, I had to install the following modules :

meteor npm install – save fibers
meteor npm install – save source-map-support
meteor npm install – save underscore
meteor npm install – save semver

Then come the last error which I can’t get rid of : Cannot find module “fibers/future”

Help me please … I can’t figure out what’s going on here.

I’m currently running Meteor and Node v8.11.1.
The first project worked yesterday but on another computer but still, the above versions were the same.

Thank you for you time !

hi @mostlyawesom, are you on Windows?
There’s currently a known issue where the latest Windows update breaks Meteor, but it might be something else…

Can you post the error you’re getting?

Hi @coagmano

Yes, I’m on Windows 7.
Here is the error log from the terminal that execute the “meteor” command

W20180507-09:54:11.678(2)? (STDERR) X:\directory\test
W20180507-09:54:11.680(2)? (STDERR) return f
n.apply(this, arguments);
W20180507-09:54:11.682(2)? (STDERR)
W20180507-09:54:11.683(2)? (STDERR)
W20180507-09:54:11.683(2)? (STDERR) Error: Cannot find module “fibers/future”
W20180507-09:54:11.684(2)? (STDERR) at Object.require (X:\directory\test.meteor\local\build\programs\server\boot.js:295:24)
W20180507-09:54:11.685(2)? (STDERR) at packages\meteor.js:143:20
W20180507-09:54:11.686(2)? (STDERR) at packages\meteor.js:313:4
W20180507-09:54:11.687(2)? (STDERR) at packages\meteor.js:1438:3
W20180507-09:54:11.688(2)? (STDERR) X:\directory\test.meteor\local\build\programs\server\boot.js:411:36
W20180507-09:54:11.689(2)? (STDERR) at Array.forEach ()
W20180507-09:54:11.690(2)? (STDERR) at X:\directory
W20180507-09:54:11.692(2)? (STDERR) at X:\directory
W20180507-09:54:11.696(2)? (STDERR) at (X:\directory
W20180507-09:54:11.697(2)? (STDERR) at X:\directory
=> Exited with code: 1
=> Your application is crashing. Waiting for file change.

Obviously I renamed my directory for privacy purpose :slight_smile:

Where did you find that the latest Windows update broke meteor ? I’d like to read it a bit.

I think I found a post with a sort of a solution : Error: Cannot find module ‘fibers’
I don’t know why I didnt find it before creating my topic …

That’s a Windows10 issue. If you’re still on 7 then it’s another problem you’re having.

1 Like

Well, :confused: any suggestion ?

Can you point me to more details about the breaking windows update? I have searched and searched and burned 2 dev days trying to troubleshoot. This is extremely important - particularly if there is a viable solution coming that does not involve using the new win10 ubuntu bash and hacking away at the symlinks, etc.

My meteor version is - here is the error output from the build
W20180507-19:35:11.808(-7)? (STDERR) C:\src\Analytics-Insights\app\node_modules\fibers\fibers.js:89
W20180507-19:35:11.808(-7)? (STDERR) return fn.apply(this, arguments);
W20180507-19:35:11.808(-7)? (STDERR) ^
W20180507-19:35:11.808(-7)? (STDERR)
W20180507-19:35:11.809(-7)? (STDERR) Error: EPERM: operation not permitted, stat ‘C:\src\Analytics-Insights\app.meteor\local\build\programs\server\node_modules’
W20180507-19:35:11.809(-7)? (STDERR) at Object.realpathSync (fs.js:1670:17)
W20180507-19:35:11.809(-7)? (STDERR) at toRealPath (module.js:156:13)
W20180507-19:35:11.809(-7)? (STDERR) at tryFile (module.js:152:22)
W20180507-19:35:11.809(-7)? (STDERR) at tryExtensions (module.js:164:22)
W20180507-19:35:11.809(-7)? (STDERR) at Function.Module._findPath (module.js:217:20)
W20180507-19:35:11.810(-7)? (STDERR) at Function.Module._resolveFilename (module.js:534:25)
W20180507-19:35:11.810(-7)? (STDERR) at Function.Module._load (module.js:466:25)
W20180507-19:35:11.810(-7)? (STDERR) at Module.require (module.js:579:17)
W20180507-19:35:11.810(-7)? (STDERR) at require (internal/module.js:11:18)
W20180507-19:35:11.810(-7)? (STDERR) at Object.require (C:\src\Analytics-Insights\app.meteor\local\build\programs\server\boot.js:283:20)
=> Exited with code: 1
=> Your application is crashing. Waiting for file change.

Ok guys, I got some news.
Today I tried my project on another computer. This time with Win 10, version 1709 (os version 16299,371).
There is no problem there. Everything works like it should. I think it’s important to point out the fact that the Meteor&Co installation on the working computer was done a while ago but still with the latest version of Meteor and Node. Basically, the same installation as on the computer that do not work.

Yes, Meteor on windows seems extremely fragile at best. We have had it break multiple times, some with no explanation but currently facing the Windows 10 1803 problem and have wasted hours trying to solve. We are planning to just move development to a Linux VM (where we have NEVER seen it break - knock on wood) going forward.

Just figuring out the best way to share the files between the VM and my Windows machine where I want to do the editing / dev work. Meteor (and not just Meteor) do not handle CIFS/SMB well as they want to create symbolic links all over the place. Thinking NFS might be fine.

1 Like

Yeah I did think of making a Linux VM but didn’t know how to do the part where you edit your code on Win and “display” it in linux. I would really love to know how you did, if you succeed, because I’m on a school project and I don’t really have that much time :confused: .

This is ending up to work for us and here is what we have at this point (though a lot of variations will work):

  1. Installed Virtualbox for the VM system:
  2. Installed Ubuntu 18.04 LTS as a guest, here are some instructions though we just installed being familiar with Ubuntu:
  3. We have a private cloud storage (something like Dropbox, Google drrive,…) and simply share the folder with the VM as there is a client. Ubuntu has client support for most, so pick one that you have access to. This would also be where I think NFS could be made to work, but that would be more complex initially.
  4. Installed Meteor inside the VM using: curl | sh under the same user hosting the files.
  5. Start the application in the VM using whatever commands you typically would.

That is is, now we can edit the files on our Windows system. When saved they sync automatically and in our case nearly instantly. Now, back to working on the application instead of attempting to fix Meteor which I still have not succeeded on (though I do not intend to work on either at this point).

Hope this helps.

1 Like

Or you can use the Linux Subsystem:

I went down that road once before, was not a happy trail for me. Others experiences may vary.

As I detailed, there are some things you have to watch out for when you set it up.

After you’ve done that it works fine. And it’s a bit less of a hassle than a fullblown VM.

I did find this docker image for meteor development that might be a good compromise: