Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade Meteor Testapp to Meteor 3.0 (Beta) #3709

Open
jankapunkt opened this issue Feb 9, 2024 · 7 comments
Open

Upgrade Meteor Testapp to Meteor 3.0 (Beta) #3709

jankapunkt opened this issue Feb 9, 2024 · 7 comments

Comments

@jankapunkt
Copy link

Meteor is closing in to a new major release with lots of breaking changes. Is this something that is relevant to this project?

@ocdtrekkie
Copy link
Collaborator

We are currently stuck a bit further behind than that, but it's definitely a goal.

@xet7
Copy link
Contributor

xet7 commented Feb 9, 2024

Kind of related, I mentioned Sandstorm at podcast today https://www.youtube.com/watch?v=zic-h8jG6F8

@jankapunkt
Copy link
Author

I'll give it a try on updating it to the Beta and see what issues arise in the process.

@ocdtrekkie
Copy link
Collaborator

@jankapunkt So the main thing I can already tell you is the standing blocker is that we use MongoDB 2.6.

@jankapunkt
Copy link
Author

Ah okay that's truly a blocker I think at a certain version of Meteor 2.x the minimal Mongo version is 5.x

@ocdtrekkie
Copy link
Collaborator

Yep. Our standing challenge is that since Sandstorm is deployed in thousands of servers owned by people who are not all technical people, we need to upgrade MongoDB in a very safe/clean way. Probably the next blocker once the MongoDB migration is tackled, is that node-capnp has not been upgraded for the latest versions of Node, and my understanding is the conversion from 14 to 16+ is non-trivial?

@jankapunkt
Copy link
Author

The Migration from Node 14 will be to 20 with Meteor 3 as they decided to keep up with the Node.js lifecycle as good as possible in order to get all the security fixes and features etc.

However, the bigger part of the Migration is actually the removal of Fibers (coroutines) as they are not supported by Node >=16 and therefore all the internal Fibers-related code is migrated to async/await. Most of all this affects nearly all functionality where Mongo.Collection is involved or where Fibers has been in direct usage.

A detailed list of what's affected is collected here: https://github.com/meteor/meteor/blob/d5c3b2eeafd0ad78ee7e2553f3f269c5c2a2e2a9/docs/generators/changelog/versions/3.0.md#L5-L17

Note this list only covers Meteor core and core-packages (like Accounts etc.) but no community packages.

Regarding the MongoDB migration I can actually help out with an article I wrote, after I wrestled with this when migrating from 4 to 5: https://dev.to/jankapunkt/meteorjs-and-meteor-up-mongodb-migration-to-a-new-major-version-40b7

However, the article is Meteor+Meteor-Up focused.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants