I just ran meteor update and was prompted that I’m now on 1.3
I looked at my versions file, and meteor is at 1.1.2
If I run meteor update again it tells me I’m currently at 1.3
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”;
W20160331-11:02:58.474(-6)? (STDERR) ^^^^^^
W20160331-11:02:58.477(-6)? (STDERR) SyntaxError: Unexpected reserved word
Has anyone had issues with FlowRouter since upgrading?
I’m getting this error client side:
There is no route for the path: /
I got into a similar situation trying to upgrade from 1.1 . In the end, I created a new meteor project and copied everything except my .meteor directory over and that fixed the problem.
That is my exact issue, I made another post about it on here as well, no responses yet!
I spent an evening thinking my imports weren’t working. I would set a breakpoint in chrome dev tools and check if the objects I needed had become available. They weren’t, but that’s because I didn’t have any code in that scope using those objects, and Meteor doesn’t load the stuff you aren’t using. I didn’t expect that, though. Hopefully this saves someone else the same headache.
1 reply
Actually… some of my imports just don’t seem to work… still trying to understand why.
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.
