Error: Cannot find module 'fibers'

PS C:\Users\[username]\fullstack> meteor create test2
C:\Users\[username]\AppData\Local\.meteor\packages\meteor-tool\1.6.1_1\mt-os.windows.x86_64\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:218
      throw error;
      ^

Error: Error: Could not install npm dependencies for test-packages: Command failed: C:\WINDOWS\system32\cmd.exe /c C:\Users\[username]\AppData\Local\.meteor\packages\meteor-tool\1.6.1_1\mt-os.windows.x86_64\dev_bundle\bin\npm.cmd install --production=false
npm ERR! Cannot read property 'match' of undefined

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\[username]\AppData\Roaming\npm-cache\_logs\2018-05-16T01_31_23_763Z-debug.log
npm ERR! Cannot read property 'match' of undefined

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\[username]\AppData\Roaming\npm-cache\_logs\2018-05-16T01_31_23_763Z-debug.log

    at Object.error (C:\tools\utils\buildmessage.js:430:11)
    at C:\tools\cli\default-npm-deps.js:36:20
    at C:\tools\utils\buildmessage.js:334:18
    at exports.EnvironmentVariable.withValue (C:\tools\utils\fiber-helpers.js:89:14)
    at C:\tools\utils\buildmessage.js:333:36
    at exports.EnvironmentVariable.withValue (C:\tools\utils\fiber-helpers.js:89:14)
    at Object.enterJob (C:\tools\utils\buildmessage.js:324:26)
    at Object.install (C:\tools\cli\default-npm-deps.js:27:27)
    at Command.func (C:\tools\cli\commands.js:801:36)
    at C:\tools\cli\main.js:1523:15
PS C:\Users\[username]\fullstack>

Whatā€™s happening here? did a reinstall and still see the error

This fix has been merged into the 1.7 branch, but is not in the latest release build (rc.11). Any idea when we will see either a new RC or a final release of 1.7? Iā€™m unable to run on Windows any longer after the April update of Windows 10. For political reasons Iā€™m unable to install WSL as a work-around.

1 Like

No idea sorry.

On the 1.7 pull request it looks like it was added 4 days ago so Iā€™m surprised itā€™s not in the latest release candidate

Maybe ask the devs on that thread? https://github.com/meteor/meteor/pull/9826

1 Like

you are spot on, this fixes it, which is great. BUT its not exactly a good build process - its like a fix to a (broken) build process that shouldnā€™t really exist - though I note meteorā€™s own build notes include the same necessary step. Any ideas how can this ā€˜fixā€™ step be avoided for a build pipeline ?

So Iā€™ve just been running Meteor --production for the last while and getting far simpler results lol.

Might not be the best way, but so far I donā€™t see why not.

I have a script that pulls github version, kills the meteor instance, swaps new files and restarts meteor --production.

Thoughts?