SOLVED: Error: Cannot find module 'meteor/tmeasday:check-npm-versions'


Issue happens to my existing project after upgrading from 1.5.x to 1.,6

Completely uninstalled Meteor from Windows 10 and installed again.

Same for new project. To reproduce

  1. Create an empty project with “meteor create”

  2. Install collection2-core
    meteor add aldeed:collection2-core
    meteor npm install --save simpl-schema

  3. run with “meteor”

[[[[[ ~\D\DEV-ML\htdocs\MeteorNix ]]]]]

=> Started proxy.
=> Started MongoDB.
W20171117-21:43:55.448(1)? (STDERR) d:\Users\markus\AppData\Local\.meteor\packages\meteor-tool\1.6.0\\dev_bundle\server-lib\node_modules\fibers\future.js:280
W20171117-21:43:55.486(1)? (STDERR)                                             throw(ex);
W20171117-21:43:55.489(1)? (STDERR)                                             ^
W20171117-21:43:55.490(1)? (STDERR)
W20171117-21:43:55.491(1)? (STDERR) Error: Cannot find module 'meteor/tmeasday:check-npm-versions'
W20171117-21:43:55.492(1)? (STDERR)     at Function.Module._resolveFilename (module.js:513:15)
W20171117-21:43:55.493(1)? (STDERR)     at Function.resolve (internal/module.js:18:19)
W20171117-21:43:55.493(1)? (STDERR)     at Object.require (D:\DEV-ML\htdocs\MeteorNix\.meteor\local\build\programs\server\boot.js:287:32)
W20171117-21:43:55.495(1)? (STDERR)     at makeInstallerOptions.fallback (packages\modules-runtime.js:651:18)
W20171117-21:43:55.499(1)? (STDERR)     at require (packages\modules-runtime.js:244:16)
W20171117-21:43:55.500(1)? (STDERR)     at collection2.js (packages/aldeed:collection2-core/collection2.js:1:345)
W20171117-21:43:55.500(1)? (STDERR)     at fileEvaluate (packages\modules-runtime.js:343:9)
W20171117-21:43:55.501(1)? (STDERR)     at require (packages\modules-runtime.js:238:16)
W20171117-21:43:55.502(1)? (STDERR)     at D:\DEV-ML\htdocs\MeteorNix\.meteor\local\build\programs\server\packages\aldeed_collection2-core.js:718:15
W20171117-21:43:55.502(1)? (STDERR)     at D:\DEV-ML\htdocs\MeteorNix\.meteor\local\build\programs\server\packages\aldeed_collection2-core.js:729:3

manually adding “tmeasday:check-npm-versions” using “meteor add tmeasday:check-npm-versions” does not help.


meteor-base@1.2.0             # Packages every Meteor app needs to have
mobile-experience@1.0.5       # Packages for a great mobile UX
mongo@1.3.0                   # The database Meteor supports right now
blaze-html-templates@1.0.4    # Compile .html files into Meteor Blaze views
reactive-var@1.0.11           # Reactive variable for tracker
tracker@1.1.3                 # Meteor's client-side reactive programming library

standard-minifier-css@1.3.5   # CSS minifier run for production mode
standard-minifier-js@2.2.0    # JS minifier run for production mode
es5-shim@4.6.15               # ECMAScript 5 compatibility for older browsers
ecmascript@0.9.0              # Enable ECMAScript2015+ syntax in app code
shell-server@0.3.0            # Server-side component of the `meteor shell` command

autopublish@1.0.7             # Publish all data to the clients (for prototyping)
insecure@1.0.7                # Allow all DB writes from clients (for prototyping)



  "name": "MeteorNix",
  "private": true,
  "scripts": {
    "start": "meteor run"
  "dependencies": {
    "babel-runtime": "^6.26.0",
    "meteor-node-stubs": "^0.3.2",
    "simpl-schema": "^0.5.0"


Hmm, try switching the order of




and see if it helps.


Thanks for this idea, unfortunately it did not help.


I just tried

meteor create deleteme
cd deleteme
npm i simpl-schema
meteor add aldeed:collection2-core tmeasday:check-npm-versions
meteor update

and the app ran successfully without a problem. Can you try this and see if you can reproduce it?


I solved it by moving the meteor installation directory to a higher directory level.

Before it was “c:\users\markus\appdata\local.meteor” now it is “c:\dev.meteor”.

No real idea why this works, might be that a path got too long, but again I don’t know.

Anyhow, my issue is resolved and can be closed.

Thanks for your help.


Huh, that’s quite interesting. I’d hope the latest version solved the long path names problems on windows. Anyway, I’m glad you figured this out.