My journey towards meteor 3.0

3.0 migration
15

I think that’s true, since preparing a PR means potentially quite some extra work for those who are already at (over) 100% load… :wink:

16

Ok, for now i finished the transition of all of my methods and pubs and have tests for my methods and rest api. The remaining warnings on fibers are coming from accounts-base, meteor-files and monti. Looking really forward for those packages to get updated.

5 Likes
17

That is a great case study, thanks for sharing your experience.

1 Like
18

Congrats!

You might want to report it here: https://github.com/meteor/meteor/pull/12359

1 Like
19

Thanks for sharing. I already feel my gray hair growing when I read all of this.

2 Likes
20

Yeah, it’s not so much fun really…
I also noticed that memory consumption is quite a bit higher when everything’s changed to promises.

Got my async update up and running in my staging environment. Monti reports RAM usage of ~300mb in contrast to ~225mb when no sessions are active…

I‘m really curious what will happen here when I get some load on the server…

1 Like
21

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 :wink:

4 Likes
22

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.

3 Likes
23

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

1 Like
24

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

2 Likes
25

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

1 Like
26

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

2 Likes
27

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)
2 Likes
28

Great job. Keep up the good work! :clap: :clap:

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

29

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.

1 Like
30

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! :heartbeat:

7 Likes
31

That’s awesome! Congrats :clap:

1 Like
32

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

33

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

34

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.

2 Likes