I have six ongoing projects where I use Meteor. I just created my sixth project, installed packages, node modules etc. Then I tried to start the project, it said following error. After that, the system cannot find the Meteor command anymore. This is the third time within four months I need to uninstall and then re-install Meteor to my Windows 10. Not very productive! Whats going on?? Very, very annoying!
Last time i have re-installed meteor 7th of April.
meteor --settings settings.json
module.js:327
throw err;
^
Error: Cannot find module 'meteor-promise’
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at makeCompatible (C:\Users\UN\AppData\Local.meteor\packages\meteor-tool\1.4.4_1\mt-os.windows.x86_32\tools\tool-env\install-promise.js:6:3)
at Object. (C:\Users\UN\AppData\Local.meteor\packages\meteor-tool\1.4.4_1\mt-os.windows.x86_32\tools\tool-env\install-promise.js:9:1)
at Module._compile (module.js:409:26)
at Object.Module._extensions…js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
This doesn’t really answer your specific question, but might solve some broader issues for you.
If your were to install your Meteor build and install environment in a virtual machine running your preferred distribution of Linux and expose its project directory as a shared directory in your Windows host, you would keep the development experience you are comfortable with, while installing, building and testing your Meteor work in the environment that gets preferred attention from developers.
For your numerous projects, you could have them in one VM each and be entirely free of any danger of interference between them. VM snapshots give the flexibility to run “dangerous” experiments in refactoring, with trivial reversion if things screw up.
Thans @warehouseman
That is a thing what should I think about! I’ll.
Anyway. I re-installed meteor, and now for my older project it won’t start anymore. Then i tried “meteor update” it gives me same error when starting the project. Very fkng annoying!
C:\Users\UNr\AppData\Local.meteor\packages\meteor-tool\1.4.4_1\mt-os.windows.x86_32\isopackets\ddp\npm\node_modules\meteor\promise\node_modules\meteor-promise\promise_server.js:190
throw error;
^
Error: No metadata files found for isopack at: /C/Users/UNr/AppData/Local/.meteor/packages/tap_i18n/1.8.2
at [object Object]..extend.loadUnibuildsFromPath (C:\tools\isobuild\isopack.js:900:13)
at C:\tools\packaging\tropohouse.js:521:21
at Array.forEach (native)
at Function..each..forEach (C:\Users\UNr\AppData\Local.meteor\packages\meteor-tool\1.4.4_1\mt-os.windows.x86_32\dev_bundle\lib\node_modules\underscore\underscore.js:79:11)
at C:\tools\packaging\tropohouse.js:520:13
at C:\tools\utils\buildmessage.js:359:18
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:352:34
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:350:23
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at Object.enterJob (C:\tools\utils\buildmessage.js:324:26)
at C:\tools\packaging\tropohouse.js:515:22
at C:\tools\utils\buildmessage.js:359:18
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:352:34
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:350:23
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at Object.enterJob (C:\tools\utils\buildmessage.js:324:26)
at Object.download (C:\tools\packaging\tropohouse.js:427:20)
at C:\tools\packaging\tropohouse.js:600:22
at C:\tools\utils\buildmessage.js:359:18
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:352:34
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:350:23
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at Object.enterJob (C:\tools\utils\buildmessage.js:324:26)
at [object Object]..extend.downloadPackagesMissingFromMap (C:\tools\packaging\tropohouse.js:597:20)
at C:\tools\project-context.js:808:25
at C:\tools\utils\buildmessage.js:359:18
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:352:34
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:350:23
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at Object.enterJob (C:\tools\utils\buildmessage.js:324:26)
at C:\tools\project-context.js:807:20
at C:\tools\packaging\catalog\catalog.js:100:5
at C:\tools\utils\buildmessage.js:271:13
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:264:29
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:262:18
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:253:23
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at Object.capture (C:\tools\utils\buildmessage.js:252:19)
at Object.catalog.runAndRetryWithRefreshIfHelpful (C:\tools\packaging\catalog\catalog.js:99:31)
at ProjectContext.downloadMissingPackages (C:\tools\project-context.js:806:13)
at C:\tools\project-context.js:283:9
at C:\tools\utils\buildmessage.js:359:18
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:352:34
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:350:23
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at Object.enterJob (C:\tools\utils\buildmessage.js:324:26)
at ProjectContext..extend.completeStagesThrough (C:\tools\project-context.js:273:18)
at C:\tools\project-context.js:265:12
at Function.run (C:\tools\tool-env\profile.js:490:12)
at ProjectContext..extend.prepareProjectForBuild (C:\tools\project-context.js:264:13)
at C:\tools\cli\commands-packages.js:1528:20
at C:\tools\utils\buildmessage.js:271:13
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:264:29
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:262:18
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:253:23
at [object Object]..extend.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at Object.capture (C:\tools\utils\buildmessage.js:252:19)
at Object.main.captureAndExit (C:\tools\cli\main.js:273:29)
at maybeUpdateRelease (C:\tools\cli\commands-packages.js:1527:8)
at Command.func (C:\tools\cli\commands-packages.js:1601:29)
at C:\tools\cli\main.js:1483:23
C:\Users\UNr\Documents\Dropbox\MoveComp\Sovellus\movecomp>
Is it possible you need to seek out and purge everything to do with Node & Npm?
I do think something in your system is interfering with your Meteor installation. Working in a freshly installed OS would free you from concerns about that possibility. With that out of the way you could more confidently pursue the other possibility – version conflicts.
1 Like