Meteor.js v3.1 is out! 🎉

Node.js to v22, the MongoDB driver to v6 and Express to v5, just got upgraded. And much more!

Check our blog post:

Special thanks to the community contributors who made this release possible: @denihs, @nachocodoner, @leonardoventurini, @StorytellerCZ, @zodern, @harryadel, @perbergland, @9Morello, @wreiske, @MarcoTribuz, @MeteorCoder, and @caffeinated10xprogrammer.

How to try it?

Installing Meteor

npx meteor

Existing projects:

meteor update --release 3.1

Starting a project:

meteor create app-name --release 3.1

Your help testing this version by creating a new app or migrating your current one will be extremely helpful!

Please give us your feedback, and if you find any issues, you can create a post here or open an issue on GitHub .


Tasks and fixes in this release:

  • Update Node to v22
  • Update Mongo Driver to v6
  • Update Express to v5
  • Include Roles into Meteor Core
  • Create meteor-perf package
  • Refactor or prepare mongo package for TypeScript (Phase 1, ~60%)
  • Fix slow HMR in Meteor 3.0
  • Remove inflight from Meteor Node Stubs
  • Upgrade elliptic in Meteor Node Stubs
  • Cordova has incomplete dependencies on build Android project within specific plugins
  • Performance benchmark suite improvements
  • Measure performance with Node v22 and --experimental-async-context-frame
  • Fix bindEnvironment is not preserving all values (thanks to @zodern)
  • Remove Underscore (thanks to @harry97)
  • Fix reify being too eager to detect TLA with false positives (thanks to @permb)
  • Fix command meteor publish --update
  • Fix slow rebuilds and HMR

Pull Requests for v3.1.0

Next Releases

  • Meteor 3.1.1 (Late-November/Early-December, 2024)
  • Meteor 3.2 (Early-January/Mid-January, 2025)
22 Likes

congrats-gif-1

2 Likes

Great work, folks! It’s fantastic to see these improvements.

1 Like

Thanks for the update, HMR issue seems to be fixed. However, running the latest redis-oplog beta causes an issue in my project, cf. this post here.

Amazing guys!!! This one is a great one :star_struck:

4 Likes

Hello, this is great. If we use alanning roles what is the impact of the new core roles package ? Where is the doc of this new role package ? Is there a migration routine to move from alanning roles to the new role packages ? Thanks a lot.

2 Likes

The roles docs should be out soon, @dokithonon! You can check the PR here.

However, we don’t have a migration guide for alanning roles. That’s a great point!

cc @leonardoventurini

1 Like

I think there’s a part in the document mentioned about migration: Roles | Docs

2 Likes

A bit later than we wanted, but we just released a video where I talked to the core team about the new features and improvements of version 3.1: https://www.youtube.com/watch?v=u7Z-BKzIX4g

I’d love to get some feedback on it :slight_smile: We want to release videos in this format more often!

4 Likes

I loved the format of this video. Great job, team! :clap: :heart:

2 Likes

Finally got to watch this over breakfast today. BEAUTIFUL production value and AWESOME leadership tone for the now-direct Developer Relations approach. Was holding my breath to see how it would go but you guys leveled-up. As a team, it is inspiring to see the unity, power, focus, and enthusiasm with a sense of purpose.

Very cool to be able to believe in those on the front lines, and did not expect that feeling to come back so strong. Being proper ninjas and well put together as a squad is a gift to the community in and of itself.

Paying respect. Also, you guys sold me on moving to 3.1 straight away. I can see any hurdles with it will be overcome. And I can see the investment being made into the core is worth real faith from the community.

2 Likes