What's the current state of Meteor 1.3?

I’ve been away from this board for a while, focusing on getting my first app live. So I haven’t followed all the discussions going on about Meteor 1.3 and am just curious what its current state is from a high-level perspective.

I mean: how easy is it to transform an 1.2 app to 1.3, what obstacles are to be expected (esp. since Meteor switched to NPM), is the current beta already mature enough for a migration test (or should I better wait a bit more time) etc.

Are there any blog posts out there that already wrote about 1.3 in general or the 1.2 -> 1.3 migration from such a condensed, high-level perspective?

1 Like

Check out the migration guide http://guide.meteor.com/v1.3/1.3-migration.html <- this is for beta 12 (currently it’s 16) but things didn’t change much.

3 Likes

I just finished a 1.2 -> 1.3 migration, the main aspects were:

  1. Switching from meteor react packages to npm and import
    here is the npm package file:

“dependencies”: {
“react”: “^0.14.7”,
“react-addons-linked-state-mixin”: “^0.14.7”,
“react-dom”: “^0.14.7”,
}

here is the meteor package list:

accounts-password 1.1.5-beta.16* Password support for accounts
accounts-ui 1.1.6-beta.16* Simple templates to add login widgets to an app
blaze-html-templates 1.0.1-beta.16* Compile HTML templates into reactive UI with Meteo…
ecmascript 0.4.0-beta.16* Compiler plugin that supports ES2015+ in all .js f…
es5-shim 4.3.2-beta.16* Shims and polyfills to improve ECMAScript 5 support
insecure 1.0.4-beta.16* (For prototyping only) Allow all database writes f…
jquery 1.11.5-beta.16* Manipulate the DOM using CSS selectors
kadira:flow-router 2.11.0+ Carefully Designed Client Side Router for Meteor
matb33:collection-hooks 0.8.1 Extends Mongo.Collection with before/after hooks for inser…
meteor-base 1.0.1-beta.16* Packages that every Meteor app needs
mobile-experience 1.0.1-beta.16* Packages for a great mobile user experience
mongo 1.1.4-beta.16* Adaptor for using MongoDB and Minimongo over DDP
react-meteor-data 0.2.5 React mixin for reactively tracking Meteor data
session 1.1.2-beta.16* Session variable
standard-minifier-css 1.0.3-beta.16 Standard css minifier used with Meteor apps by def…
standard-minifier-js 1.0.3-beta.16 Standard javascript minifiers used with Meteor app…
tracker 1.0.10-beta.16* Dependency tracker to allow reactive callbacks

  1. Ran into a flow-router bug , patched the package locally
    https://github.com/kadirahq/flow-router/issues/552

  2. add import {React} to all jsx files ,since React is no longer global

  3. switched numerous globals to exports/imports

so far it looks like this is the full extent of my migration

1 Like

@brajt - thanks for sharing the migration guide link. Also, where can one track what is the most current beta and what changes have been made for the respective beta version?

Say, I need all globals (like 30 of them) in every file - do I have to prepend each of my files with 30 lines of same import code?

You could use this pattern from mantra. Essentially pull everything into one file and just import that.

1 Like

Upgrade tutorial w/ FlowRouter: https://voice.kadira.io/getting-started-with-meteor-1-3-and-react-15e071e41cd1#.jh35i6aee

you mean, one object?

@waldgeist there is a brand new blog post on the matter of 1.3:

https://themeteorchef.com/blog/meteor-1-3-from-a-20-000-foot-view/

3 Likes

Yeah, but you could easily extract each attribute e.g.

import Globals from 'lib/globals.js';
const { Global1, Global2 } = Globals;

Or you could export each global individually:

lib/globals.js

export Global1
export Global2

Then import them with

import { Global1, Global2 } from 'lib/globals.js';

Or you could simply keep using your globals as before. I believe backwards compatibility means this will still work.

1 Like
1 Like

Thanks, such a high-level overview is just what I was looking for!

@brajt - perfect, thx! So obvious after you sent the link to the releases page. :blush: