Moving app from 1.3 to 1.4


Yo team,

I tried updating my large app from 1.3 to 1.4. Did not have a clue to fix all these errors. So looks like I will be keeping it in 1.3 and Blaze.

Is there any video tutorials to make a social media app with 1.4, React and whatever those imports are?

One of the most confusing things about Meteor is all these books are written in different versions of Meteor. I am content that I know enough to finish this project in 1,3, but I would rather be working with the latest. After I learn react, I will try convert to whole thing to react.

And no, I dont think the updates in the Meteor blog explain things properly.


You should be able to update your 1.3 app to 1.4.x and still have it work properly. MDG has gone to great lengths to make sure 1.4 is backwards compatible with 1.3 (and earlier) versions of Meteor. Can you give us a few examples of the errors you’re seeing?


I think it would be easier for people to help if you posted what errors you have. Then maybe we can improve the update directions for other people. We tried our best!


I second that @repsonsive because my app was working when it was on and by the time upgraded to in order to be able to deploy to mup instead of mupx, then realized my app failed silently in my main business logic. So only when I reverted back the previous .babelrc, package.json and webpack.config.js on did it all worked properly. This is a bit difficult to find out and debug.


“Your development database is using mmapv1, the old, pre-MongoDB 3.0 database
engine. You should consider upgrading to Wired Tiger, the new engine. The
easiest way to do so in development is to run meteor reset. If you’d like to
migrate your database, please consult


W20160922-11:46:08.764(2)? (STDERR) Note: you are using a pure-JavaScript implementation of bcrypt.
W20160922-11:46:09.260(2)? (STDERR) While this implementation will work correctly, it is known to be
W20160922-11:46:09.262(2)? (STDERR) approximately three times slower than the native implementation.
W20160922-11:46:09.262(2)? (STDERR) In order to use the native implementation instead, run
W20160922-11:46:09.263(2)? (STDERR)
W20160922-11:46:09.263(2)? (STDERR) meteor npm install --save bcrypt
W20160922-11:46:09.264(2)? (STDERR)
W20160922-11:46:09.265(2)? (STDERR) in the root directory of your application.
W20160922-11:46:12.446(2)? (STDERR) /home/responsive/.meteor/packages/meteor-tool/.1.4.1_1.139xb76++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:280
W20160922-11:46:12.448(2)? (STDERR) throw(ex);
W20160922-11:46:12.448(2)? (STDERR) ^
W20160922-11:46:12.449(2)? (STDERR)
W20160922-11:46:12.450(2)? (STDERR) TypeError: Cannot read property ‘createDataHandler’ of undefined
W20160922-11:46:12.450(2)? (STDERR) at setLabels (packages/meteorhacks_kadira/lib/hijack/set_labels.js:12:1)
W20160922-11:46:12.451(2)? (STDERR) at packages/meteorhacks_kadira/lib/hijack/instrument.js:33:1
W20160922-11:46:12.452(2)? (STDERR) at runWithAFiber (packages/meteorhacks_meteorx/lib/server.js:33:1)
W20160922-11:46:12.452(2)? (STDERR) at packages/meteorhacks_meteorx/lib/server.js:26:1
W20160922-11:46:12.453(2)? (STDERR) at Array.forEach (native)
W20160922-11:46:12.453(2)? (STDERR) at packages/meteorhacks_meteorx/lib/server.js:25:1
W20160922-11:46:12.454(2)? (STDERR) at /home/responsive/Sandbox/Subpattern 1.4/.meteor/local/build/programs/server/boot.js:299:5