My journey towards meteor 3.0

[bratelefant]

Ok guys, I’m rolling out my update (still on 2.12, but with tons of internal changes moving from fibers to async). Keep your fingers crossed

[janeer]

The improvements in performance and stability are impressive. The build times have significantly decreased, making development much smoother and faster. I used to experience frustrating delays during the build process, but now it’s a breeze. Also, I think the support for the latest JavaScript features and packages has been a major boost.

[alimgafar]

@bratelefant

At the moment I only do really important hotfixes on my main branch and try to merge changes into my async branch (which is a 100% merge conflict all the time…). Feature requests are stalled. Since my async branch changes touches hundreds of files I’m really glad that by now auto merging async in my main branch seems to work.

When I got my server functions ready and tested, I’ll merge them into my main branch, so that I can potentially add features or fix bugs for production more easily.

How is it going? Are you still on 2.12? Are you considering 2.13? Have you tried using the 3.0 alpha?

[bratelefant]

Sorry for the late reply. I actually came across several packages, including Accounts, that still caused fiber warnings. On some I did a PR (like roles) and some I replaced with my own code (like meteor-tenancy). Meteor files is also an important package I think.
I didn’t yet upgrade to 2.13. Will give it a shot on my staging env on scalingo to see if building the app works as expected

[alimgafar]

Keep me informed. We mentioned this post in the MeteorJS Dispatches podcast.

[xet7]

I did post about my progress of upgrading WeKan to Meteor 3.0 alpha 15 here:

Announcing How to migrate your application to async methods and be ready to 3.0 guide

Here is my progress of upgrading WeKan to Meteor 3.0 alpha 15:

[bratelefant]

Brief update:

• PR for Meteor-Files is in the making, beta is out.
• The only remaining warnings with WARN_WHEN_USING_OLD_API=true come from the accounts-password package
• Got some trouble with updating to alpha resp. beta (cf. this thread)

[harry97]

Great job. Keep up the good work!

Consider cross posting here for reference
https://forums.meteor.com/t/looking-for-help-migrating-packages-to-meteor-3-0/

[bratelefant]

Yay! Got the first boot up of my app on meteor 3.0 beta! Wow! Worked around this issue by removing and re-adding packages step-by-step.

First a got a bit stuck at aldeed:collection2, didn’t read that you need to import 'meteor/aldeed:collection2/static'; to keep things working as before.

Now I’m a bit stuck with this problem here, related to Meteor.userAsync() calls from within publications, that throw an error. Will try to get a minimal reproducible example ready.

[bratelefant]

This may be a very old thread, but I just wanted to add: All 1500+ server tests successfully passed under 3.0.2. What a day! Thanks to everyone who helped make Meteor 3.0 possible!

[denyhs]

That’s awesome! Congrats

[MeteorCoder]

Thanks for paving the path and sharing your experience. How did you replace meteorhacks:picker?

[harry97]

It’s no longer needed, Meteor 3.0 uses express under the hood.

[bratelefant]

Next big step accomplished. Just deployed my meteor 3.0.3 update in my staging env at scalingo. Now some end-to-end testing before deploying to production.

[bratelefant]

Finally! Updated my app to 3.0.4. Everything’s looking good except from memory consumption. Needed to scale up in order to keep my containers running, that’s really a bummer. Has anyone any advice how to profile memory consumption? I’d really like to optimize this, I suspect that observers eat up more memory, but I don’t know a way to analyze this in detail.

[nachocodoner]

We’ve released the beta for 3.1.1, featuring Meteor runtime performance improvements, including reduced RAM usage. When the official version is out, we’ll share detailed benchmarks report and comparisons with earlier versions.

In the meantime, if you can help with testing, update your app and let us know if you notice any improvements in RAM usage.

meteor update --release 3.1.1-beta.1

[dokithonon]

Hello,
I have just installed it and i noticed a few of this errors at my app startup :

allow: The "updateAsync" key is deprecated. Use "update" instead.

deny: The "insertAsync" key is deprecated. Use "insert" instead.

Do you know if something has changed here ?

[nachocodoner]

Yes, we did a deprecation on allow/deny rules, to only enable insert, update and remove rules, with async validation option.

Tweaks on allow/deny rules

However, it seems that if it isn’t your direct app code, it may be related with a package using async rules and not migrated. We may consider to remove these warnings if it is the case, and treat the deprecation as a changelog item. In a future minor version we will completely remove those rules, but we would like app or packages affected to migrate already.

[bratelefant]

I’ll definitely try this, as soon as I can use montiapm on 3.1. Also, I’m quite sure that after updating to 3.0.4 from 2.16 I introduced memory leaks, since RAM keeps constantly increasing over a busy day. I already checked several “.observe” calls and checked whether the handlers got stopped.

Any hint where the transition from 2.16 to 3.0.4 could possibly introduce memory leaks? Any tools that I can use to investigate which function or variables pile up in memory? My codebase is quite large, I need to find out where to look at…

[dokithonon]

Ok thanks, this comes probably from a package because I only use this in my code :

blabla.deny({
    insert() {
    return true;
    },
    update() {
      return true;
    },
    remove() {
      return true;
    }
  });