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.