Announcing Meteor 1.3.2.2

announce
5

Updating broke my use of the changed callback in the observe cursor of a local minimongo collection…

Collection.find({}).observe({
  changed: function(new) {
    if (new._id == "id") {
      indicatorVar.set("id", new.data);
    }
  }
});

I will open an issue. Edit: here is the issue: https://github.com/meteor/meteor/issues/6849

Also had to meteor remove momentjs:moment and replace with npm install moment from npm

6

Good to see a faster release cycle. :thumbsup:

4 Likes
7

Agree. Your effort to release often @benjamn is awesome thanks again for all of your hard work :smile:

1 Like
8

So - this happened after my update.

mymeteorapp: updated to Meteor 1.3.2.2.
=> Errors while upgrading packages:
While checking for momentjs:moment@2.13.0:
error: No compatible binary build found for this package. Contact the package author and ask them to publish it for your platform.

But moment() works as it did before. Should I be worried?

1 Like
9

You can install moment via NPM, I have it working in my app.
Remove the meteor package and just save it to node_modules.

10

@benjamn thanks for the informative post on the update! this seems to have fixed an issue I had

Not sure if you knew about it, but it was very frustrating to diagnose.

11

What do you type in the terminal to do that? I tried this morning but couldn’t get it working.

Ended up just reverting to 1.3.1 (first time I’ve had to do that since 0.5.7).

12

First remove the package:
meteor remove momentjs:moment

Now install via npm with:
meteor npm install moment

Use it in your app with:
import moment from 'moment'

13

Thanks @cstrat.

Any easy way to get the moment symbol global?

1 Like
14

I remember someone explaining a way to make something global, so pretty sure you can do it! However I haven’t done it myself.

Whenever I reference moment - I just import it at the top of the file.
Maybe someone else can jump in and answer this one, sorry I don’t want to tell you the wrong thing :blush:

15

All good. Thanks for your input. I’ll do some Googling. :grin:

1 Like
16

Thank for the commands, cstrat.
But how do I change the locale without access to moment object?

17

You could always import it then make it global yourself. Something like:

  1. /imports/startup/client/globals.js:
import moment from 'moment';
window.moment = moment;
  1. /client/main.js:
import '/imports/startup/client/globals.js';
console.log(moment());
3 Likes
18

Yep, I get how that would work. I’ll definitely run with this if the momentjs:moment package doesn’t get updated in the next day or two.

(Thanks for this – I’m not particularly au fait with my imports yet, but those little codes snippet clear a few things up!)

[EDIT: momentjs:moment did get an update that works with 1.3.2.2]

19

Should aliasify work with this release or with Meteor build tool?

20

Probably a silly question, but after I did a meteor update and then meteor --version it’s still showing version 1.3.1. Shouldn’t it say 1.3.2.2? I was on 1.2.1 before the update. I tried running the update a second time, but it said that I was already running the latest. This is on Windows 10-X64.

21

Try:

meteor update --release 1.3.2.2

I had to manually set the version flag for it to work.

22

Ta - that’s working. :slight_smile:

23

Well, actually, it LOOKED like it was working, however issuing meteor --version still reports 1.3.1

24

Not a silly question at all! We unrecommended 1.3.2.2 yesterday because we realized it contained a breaking change/improvement to DDP that wasn’t intended to be released until 1.3.3. Specifically, at least one package that relied on private methods of the DDP client Connection was broken in 1.3.2.1 and 1.3.2.2.

Though you can still manually meteor update --release 1.3.2.2 with no problem, and you may even notice some nice performance improvements due to DDP update batching, we’ve unrecommended it until we can publish a 1.3.2.3 (soon) without those changes.

Sorry for the confusion!

2 Likes