Migrating to Meteor 1.3

[foobarbecue]

Actually… some of my imports just don’t seem to work… still trying to understand why.

[trajano]

If require works, it could be that your import statements are not the first non-code elements of your file. import needs to be in the top only.

[tmeasday]

@alonflowhub

meteor is at 1.1.2

The meteor package in .meteor/versions is different to the Meteor release in .meteor/release. That’s the file to check.

[spowage]

A comparison of meteor list on the old app and meteor list on a newly created app
for 1.3 will show the missing components.

Without adding the components listed from the newly created app you cannot
use the “import” keyword

A simple but critical step for upgrading to 1.3 when npm is needed.

[suhaila]

@wesleyfsmith that may mean that your application is not loading correctly. It has nothing to do with FlowRouter i think but rather something wrong with your application. May be you are missing some modules etc.

[jesperwe]

Yes I am seeing the same thing. Are you by any chance using useraccounts:… packages? Because I see the error on the FlowRouter initialization made by useraccounts:flow-router. Although that might be just because it is the first FlowRouter calls to happen in the app…

[gadicc]

@alonflowhub:

I’m trying to use import for an npm package, and I get this error:
W20160331-11:02:58.473(-6)? (STDERR) import barcode from “bwip-js”;

Sorry, I glossed over this too quickly. Npm packages aren’t processed by Meteor build plugins. It’s up to the npm package author to decide on which targets he builds for. It’s quite common today to find packages that automatically convert everything to ES5 (“old” javascript) before publishing, via babel (just like what Meteor does).

Also important to note that for server side npm packages, authors don’t usually bother to transpile with babel, because a lot of the ES6 features are already in node. Unfortunately Meteor 1.3 still uses quite an old version of node without these features, but the goods news is that this has been earmarked as a priority for the next few releases.

For now, as you noticed, it’s possible to change the imports by hand. You could also “convert” the module using babel; you can google how to do that if you want… but no need to worry with that if you already have it working.

[andylorenz]

I’ve had exactly the same issue with IronRouter - as in the same equivalent message. Never had to change my code for any meteor releases before, 1.3 is the first update that has broken my app

[Spyridon]

I am using the useraccounts package. As well I am using the alethes Pages package… Does anyone else encountering this issue happen to be using that package too?

(Edit: @wesleyfsmith confirmed that he is using the Pages + Flow packages, and removing Pages package fixed the problem!

It looks like Pages is in need of a fix! There’s some forks out there but I have not tried them to see if they fix the issue!)

[krizzii]

Are there any nice Meteor 1.3 open source project except the todos?

I am currently refactoring an app to 1.3 and it would be nice to see more examples

[sashko]

Here’s one!

Simple CRM - A line-of-business app example in Meteor 1.3, React and Redux

Hey all, I’ve spent the last 8 weeks learning JavaScript, Meteor, React and Redux from the ground up in order to evaluate Meteor as a tool for use in our company. Our bread and butter work is line-of-business apps for SMEs; we write the boring everyday apps that companies use to manage CRM, orders, production etc. To work out how good a fit Meteor is for that type of work I’ve written a little CRM and orders app called Simple CRM that includes all the bits I need on a regular basis, namely: …

[krizzii]

Awesome! Thank you sashko

[michelfloyd]

Hey @sashko, can event maps not now be documented with the more concise function format? Ex:

'click #myButton' (event){}

instead of:

'click #myButton': function(event){}

[trajano]

Are there any breaking changes to the publish subscribe functions that may cause percolate:find-from-publication to break? Percolate:find-from-publication and Meteor.users

[sashko]

The Meteor guide documents them in this way, I’d be more than happy to accept a PR changing the docs as well (those live as a Meteor app in this directory: https://github.com/meteor/meteor/tree/devel/docs)

[michelfloyd]

Do you think it would be cleaner/simpler for people? If so I’ll happily submit a PR

[sashko]

Absolutely! I think using the object method shorthand is definitely the right way to write events. All of the code samples in the Meteor Guide do it, I think we just haven’t taken the time to update the docs with all new ES2015 stuff. (see the Blaze guide article here: http://guide.meteor.com/blaze.html)

[michelfloyd]

Modified /docs/client/full-api/api/templates.md and submitted PR. Removed all the other uses of function in that file while I was at it.

[noveltysa]

I have been struggling to get my app to run in 1.3 I have Error: “There are no routes on the client or server” I have tried both Iron Router and FlowRouter, route definitions are not being pick up. I have tried place and import my router.js in almost every directory according to the new recommended app files structure.
Is there something I could be missing? What’s strange is the two examples leaderboard(1.2way) and todos-master(1.3way) both compile and work fine in 1.3.

[corvid]

A question:

In order to control load order of files, I put everything in packages.
Given the introduction of import and export, is there any benefit to having locally built packages now?