Uncaught TypeError: Cannot read property 'versions' of undefined at autoupdate_client.js

[lgleim]

With Meteor 1.8, when trying to include the bundled meteor-client.js file as usual, loading the page fails with a fatal error:

Uncaught TypeError: Cannot read property 'versions' of undefined
    at autoupdate_client.js (meteor-client.js:40145)

The issue is that the __meteor_runtime_config__.autoupdate property in the bundled client is undefined:

[lgleim]

I submitted a proper bugfix in upstream meteor code: meteor/meteor#10281

For the time being, a workaround is to add corresponding runtime configuration to the meteor-client.config.json, e.g.

{
  "runtime": {
    "DDP_DEFAULT_CONNECTION_URL": "http://localhost:3000",
    "ROOT_URL": "http://localhost:3000",
    "autoupdate": {
      "versions": {}
    }
  },
  "generateNodeModules": true
}

[KeithGillette]

Thanks for the forthcoming fix, @lgleim. This happens to us even though we're still using Meteor@1.7.0.4 locally. Is there a way to pin the Meteor release or package versions in meteor-client-bundler? This is not the first time that Meteor releases we haven't even installed have broken our build process, sorely tempting me to remove Meteor from our client altogether.

[lgleim]

Hi @KeithGillette, I am in no way familiar with the inner workings of the meteor bundling/build process but from the meteor-client-bundler documentation I suppose that is what the release config option might be there for (c.f. Readme). The best way to find out though would probably be looking at the code of this project though