Hiyas,
I’m the defacto maintainer of a number of Meteor packages and I’m considering whether to maintain support for Meteor 2. It’s difficult because more and more modern dependencies have Node.js 18 as a minimum version and Meteor 2 relies on Node.js 14.
I have a couple of question:
We have a few Meteor 2 instances in limbo. Basically, they started off as a fork of our main branch, never got merged back in, and just took on a life of their own.
And the main branch is happily sitting on the bleeding edge with Meteor 3.
We just don’t want to migrate them to Meteor 3 because the “rogue forks” feel like technical debt that should’ve been addressed earlier. For the most part our plan is just to eventually make them obsolete, migrate users to alternatives, and/or replicate any unique functionality in the main branch, which will hopefully be soon.
As far as I know, we don’t appear have any particularly strong dependency on a Meteor 2-only package (or package versions) in any of those forks.
Following our meteor metrics, in December for 2.x: we had 23640 meteor run, 580 meteor bundle and 61 meteor deploys
WeKan still uses Meteor 2. @harry97 is helping with upgrading to Meteor 3. Any additional help is very welcome.
Yeah, I’m still using 2.x. Moving over thousands and thousands of methods on a heavily used production app is daunting, and I haven’t embarked down that path.
At Monti APM we record the Meteor versions of the apps we monitor, partly to help with this type of question and for some features (I’ve been wanting to build alerts for when an app is using an insecure Meteor release).
The most popular Meteor release among the apps we monitor is Meteor 2.16 by far. The second is Meteor 3.3.2, with half the number of servers as for Meteor 2.16. Actually, the total number of servers running Meteor 3 is about the same as the number for just Meteor 2.16. If you decide to support Meteor 2, 2.12 - 2.16 should cover most apps.
Security is a huge missing link in Meteor APM land. sblaisot did inquire about Meteor packages alerting/monitoring in the official slack before. I could only direct him to GitHub - East5th/package-scan by @pcorey / Pete Corey - Meteor Package Scan
You heard of AI? That’s the classic use case for the current state of AI.
Yes, I use Claude Code heavily. Handling 1,000+ methods is unfortunately not a straightforward task for Claude Code just yet, and given that I have 100,000+ MAU it’s something I need to be quite careful about 