Meteor 1.4.2.1 is an important patch for 1.4.2 users


#21

I gave up at last. Just uninstall the meteor and then reinstall it. Have the last version now. :slight_smile:


#22

Since the update I get strange messages in the console client side

Exception in template helper: Error
    at exports.check (http://localhost:3000/packages/check.js?hash=d4de24f57efd5d716b6ce9a7a90bf6a91b307bf4:67:15)
    at Object.<anonymous> (http://localhost:3000/app/app.js?hash=f539d4f234ce1ef54e997cf9351729d9aa12f3ee:37039:5)
    at http://localhost:3000/packages/blaze.js?hash=24be3cac02f183a21bdc239399e1747c4952f799:3035:16
    at http://localhost:3000/packages/blaze.js?hash=24be3cac02f183a21bdc239399e1747c4952f799:1697:16
    at http://localhost:3000/packages/blaze.js?hash=24be3cac02f183a21bdc239399e1747c4952f799:3087:66
    at Function.Template._withTemplateInstanceFunc (http://localhost:3000/packages/blaze.js?hash=24be3cac02f183a21bdc239399e1747c4952f799:3728:12)
    at http://localhost:3000/packages/blaze.js?hash=24be3cac02f183a21bdc239399e1747c4952f799:3086:27
    at Spacebars.call (http://localhost:3000/packages/spacebars.js?hash=dcb91068ed863bb067d30163ef7df2825655ee2f:172:18)
    at Spacebars.mustacheImpl (http://localhost:3000/packages/spacebars.js?hash=dcb91068ed863bb067d30163ef7df2825655ee2f:106:25)
    at Object.Spacebars.mustache (http://localhost:3000/packages/spacebars.js?hash=dcb91068ed863bb067d30163ef7df2825655ee2f:110:39)

There seem’s to be an error with the check function but to figure it out is outta my league :slight_smile:
(the app still work fine though and yes I did installed the required babel-runtime)
Can somebody throw me a bone here ?
Thanks


#23

I download the officially provided InstallMeteor.exe and install it in China, but it failed from time to time.
The speed of downloading Meteor during installing is much slower than ever before. Why so ?

Is there any offline-installer provided for Meteor?
Thanks.


#24

Tried now, same higher cpu usage with that parameter true or false. However I believe this cpu increase happens only in development environment (hopefully) for better rebuild times so I’ll take a stab on updating my production servers with the latest version.


#25

Same thing here macos 60% cpu with Meteor 1.4.2.1, 16% for Meteor 1.4.2 (i found this pretty high too…)


#26

Since I updated I am getting a lot of these errors:

=> Started proxy.
=> Started MongoDB.
/Users/PolGuixe/.meteor/packages/coffeescript/.1.11.1_3.7g1l85++os+web.browser+web.cordova/plugin.compileCoffeescript.os/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:190
      throw error;
      ^

Error: ENFILE: file table overflow,

Originated from different files


#27

meteor-tool is the bane of every Meteor developer. it’s paaiiiin. and never asks permission.


#28

Maybe I’ve been lucky, but I’ve never had a problem.


#29

The meteor tool is one of the main reasons I started with Meteor and have stuck with it for 3.5 years. It’s given me the occasional non-intractable problem but, on balance, has saved me hundreds of hours.


#30

I am now with version 1.4.2.3.
It seems every time I create one new project, it requires meteor npm install --save babel-runtime?
Any idea to avoid this permanently?


#31

I have the same problem.


#32

The need to install babel-runtime is explained here.


#33

npm install --save babel-runtime - it help for me, thanks


#34

I understand the need for it, but since it is suggested on every new project, it should just be done automatically


#35

I kind of agree, and kind of disagree. Technically, babel runtime is NOT needed for meteor core to function. It’s only needed if you want to use ecmascript package. That said, those users who have the knowledge to make these fine-grained decisions can choose for themselves whether they need it, while the default would have it in for everyone. Biggest issue then is communication.