Henrique Schmaiske has guided Meteor.js through its largest update in over a decade with the release of Meteor 3.0, impacting many developers. ➡️ dataconomy.com/2026/06/12/ho… #MeteorJS dataconomy.com/2026/06/12/ho…

Still on Meteor 2? 👀 It reached End-of-Life in December 2025, which means no more updates of any kind. But hey, migrating to Meteor 3 is more approachable than it looks. This new guide on the blog covers what changed, what breaks, and how to fix it: blog.galaxycloud.app/meteor-…

Meteor 3.5-rc.1 is out! Change Streams on by default, a pluggable DDP transport (uWebSockets), DDP Session Resumption, MongoDB Collation, Node.js 24.15.0, and more. This is the final checkpoint before 3.5. Give it a try: meteor update --release 3.5-rc.1

@meteorjs release 3.5-rc.1 is out 🎊🎉🥳 All the details: Change Streams on by default, the new pluggable DDP transport (uWebSockets), DDP Session Resumption, `accounts-express`, async DDPRateLimiter matchers, MongoDB Collation, the EJSON/DDP performance batch, Node.js 24.15.0, and the full list of fixes, are already covered in the main post here: forums.meteor.com/t/meteor-3… Give it a try: meteor update --release 3.5-rc.1 This is the final checkpoint before 3.5 official, so the most valuable thing you can do right now is test your apps against `3.5-rc.1` and report anything unusual here in the thread. Your feedback is what gets us to a solid stable release. 🙏 Thanks again to everyone who contributed and tested along the way!

yeap, sure thing

can you use these upgrades without the rspack stuff?

Use it with ostrio:mailer package for efficient scaling and fail proof retries

吃瓜发现这个女孩子 @qiqing 居然是我互关，甚至就在 2012 年。当时我好像是写了几个 MeteorJS 包，她在 Meteor 工作，给我寄了一大包各种尺寸的 T 恤，我穿了好多年

@meteorjs is leveling up, and it's time our community structure reflects the true maturity of the framework. ☄️📈 As the ecosystem continues to grow, relying solely on informal trust and the heroic efforts of a few maintainers just doesn't scale anymore. That’s why we just opened PR #14426, introducing the first official GOVERNANCE.md for MeteorJS. This isn't about adding bureaucracy, it's about setting us up for the next decade. We are decentralizing technical leadership and creating a clear, professional path for anyone who wants to get deeply involved: 👉 Clear progression paths: Everyone will know exactly how to go from a casual Contributor to a Core Committer, and eventually, to the TSC (Technical Steering Committee). 👉 Domain Expertise: We are defining "owners" for specific areas of the framework (like DDP, Reactivity, Build System) to speed up reviews and distribute the load. 👉 Roadmap Alignment: Helping channel our community's incredible energy into the things that actually drive the framework forward. We opened this PR as a Draft because I want this to be a collective effort. I’d love to hear your thoughts on this new decentralized governance model. Do you feel this structure will help you contribute more easily? Let’s discuss the next chapter of Meteor. Drop your feedback in the PR or here in the replies! 👇 🔗 github.com/meteor/meteor/pul…

Not that I’m aware of, but that’s a great idea

This week I’ve updated “flow-router” a core routing library of @meteorjs apps. Now library ships with Agent SKILLS.md! Simplifying Meteor.js development in the age of AI #webdev #oss #javascript

Excited to see @remix_run folks innovating! I wonder though how they define "truly full-stack" in "world's first truly full-stack JavaScript framework" (from Remix 3 web) when Wasp, BlitzJS, RedwoodJS and MeteorJS (and probably some more I missed) don't seem to qualify ;).