What's left until an official Meteor 3.0?

[denihs]

Our work to remove Fibers from Meteor began in 2021, which you can read about here. We’ve made significant progress and are now close to releasing an official version of Meteor 3.0 without Fibers and running on Node.js 20.

For those new to this, Fibers was our way of handling promises, but it’s not compatible with Node.js 16 and onwards. We're moving to async and await to match Node.js standards and community practices.

For background on Fibers and this change, check the discussion.

We’re in the last phase of this transition but still have much to do. This document outlines the remaining steps and will be continuously updated to keep the community informed.

Estimated Release Dates

• Last Meteor 3.0 Beta: March 26, 2024
• First Meteor 3.0 RC: April 19, 2024
• Next RCs and Official: We need your help testing and providing feedback.

---

Meteor Releases

Meteor 3.0 Alpha (Finished)

• Unhandled Rejection when fails to bundle the app [denihs] [PR]
  • If the app server breaks, instead of waiting for changes, an error is thrown, and the app goes down.
• Review Meteor.call, Meteor.callAsync, Meteor.apply, Meteor.applyAsync [radekmie, denihs]
  • We should review these methods to understand what's the best use for them. Today, Meteor.callAsync is the biggest problem. We solve most of these problems with some flags. But this isn't optimal, and we must find a good solution. For more context on this, we have this PR and this discussion.
• Update Node to version 20. [denihs] [PR]

Meteor 3.0 Beta (Finished)

• Circle CI tests failing for external packages [Group 3]. [denihs] [PR]
  • Some tests are still failing in this Group.
• Circle CI tests failing for external packages [Group 5]. [denihs] [PR]
  • Some tests are still failing in this Group.
• Error with Source-map showing up in some cases. Context.
• Insert not working for collections created of the fly. Context [nachocodoner].
• Fix Async iterators for Meteor 3 context
• Review observeChanges - #12918 [Meteor 3] Mongo.Cursor.observeChanges returns a Promise instead of a query handle [nachocodoner][PR]
• accounts-password: Meteor.user() doesn't return the user inside a Meteor.createUser() anymore. [denihs] [PR]
  • Some tests heavily depend on the behavior, like [this one].(

    meteor/packages/accounts-password/password_tests.js

    Lines 132 to 134 in ce22f2d

    	Accounts.createUser(
    	{ username: this.username, email: this.email, password: this.password },
    	loggedInAs(this.username, test, expect));

    ). This was the workaround used to make the tests pass. It's not the ideal solution. We need to understand why this was happening and fix it.
• Fix minifying lazy stylesheets.
• It is required for Tailwind to work. The minifier is given the content as a promise instead of as a string, which causes the custom minifier - devel vs prod test to fail.
• Fix Linker bug [denihs] [PR]
  • In this commit, we introduced a hack to avoid returning the same file more than once in the function getPrelinkedFiles().
• Fix springboarding and warehouse [denihs] [PR]
  • We need to fix springboarding before releasing a beta. These are tested at tools/tests/update-tests.js.
• [Meteor 3] Uncaught Promise Rejection when throwing stub error #12950 [nachocodoner]
• Symlink error when installing Meteor with NPM [nachocodoner]
  • It seems that when installing Meteor 3 with npm, we get some errors related to symlink

Meteor 3.0 RC (Started)

• ⛏️👷 Remove any and all references to fibers throughout the code base. [denihs]
• Uncaught Promise Rejection when throwing stub error [nachocodoner] [Issue] [PR]
• Support Linux ARM with the Meteor installer [nachocodoner] [PR]
• ⛏️👷 Did not check() all arguments Error [nachocodoner] [Forum Post]
• Log use of deprecated Mongo methods only for App uses [Forum Post]
• Remove the pinned version of packages inside the skeletons.
  • Remove react-meteor-data pinned versions.
    • We had to pin this version because, as react-meteor-data is not a core package, it'll always get the latest version (v2 right now) when creating a new app
  • Remove jorgenvatle:vite-bundler pinned versions.
• Update NPM, Node and TypeScript to latest versions [nachocodoner] [PR]
• Circle CI tests failing for external packages [Group 5]
• Sequential packages loading order [radekmie] [PR]
• Using module-resolver plugin in babel throw false-positive [issue]

Meteor 3.0 Official (To-Do)

We need your help testing and providing feedback once the RC (Release Candidate) is out.

Meteor 3.x (To Do)

• Bring / Update community packages
  We want to bring some community packages to the core: meteor-migrations, meteor-synced-cron, and meteor-collection-hooks.
• Check how we could enable native ES modules on Meteor. Context

---

Blaze (Finished)

• Decide if any changes are necessary for the Async States in Blaze (remove Experimental warning from docs). [radekmie] [PR]
• Discuss and decide what makes more sense within Async State Sync.
• Check firstRunPromise discussion. [radekmie] [PR]
• Support for async attributes <div class="static {{dynamic}}" />. [radekmie] [PR]
• Support for async attribute spreads <div {{dynamic}} />. [radekmie] [tracking issue] [PR]
• Measure the performance impact of all async-related changes. [radekmie] [tracking issue]

Meteor 3.0 Documentation (Started)

• ⛏️👷 Update Meteor API Docs to v3 and migrate to Vitepress [Grubba27]
  • https://v3-docs.meteor.com
• Guides
  • ⛏️👷 How to migrate to Meteor Async in Meteor 2.x
    • We are working on our own version, but led by Daniel Dornhardt, the community is also working on one. You can check the current document here and also the post in the forum.
  • How to migrate from Meteor 2.x to Meteor 3.0
• Update Tutorials
  • Update Meteor 3.0 with React Tutorial
  • Update Meteor 3.0 with Blaze Tutorial

Independent releases (Started)

• Update Meteor 3.0 to use Reify 0.25.1
  • Some places are still using version 0.24.0
• Review compiler-plugin addStylesheet.
  • We have a partial fix for stylesheets that we need to make if we want to keep them. For more context.
• CoffeeScript
  • Test everything related to CoffeeScript and make sure it works.

Performance / Helpers (To Do)

• Email package
  • Analyze if it's possible and/or if it has good performance even using TLA.
• Improve HMR performance
  • Make sure the changes we did with HMR don't hurt the performance. For more context.
• Create a stress test to compare data between Meteor 2 and Meteor 3, now without Fibers and Node 20.
  • We want to create materials comparing Meteor 2 and 3 performance.
• Evaluate how we can create tools to help in the migration process.
  • The community has created a Codemod, Meteor packages and ESLint plugins.

⛏️👷 means someone is working on it

[markpdev2]

Hi just checking ETA of 3.0 beta -- thanks heaps

[rj-david]

https://forums.meteor.com/t/whats-left-until-an-official-meteor-3-0/60775

[trusktr]

I see accounts-password on the list, but I think accounts-ui needs to be on the list too, as that had a constraint error when I tried to upgrade to 3.0 beta.0.

[trusktr]

It would be really great if native ES module (ESM) support is slated for 3.0. Meteor is already lagging behind, and if 3.0 comes out without native ES module support, it'll just still be lagging behind in a fairly critical way: the ecmascript package compiles all code to an internal CommonJS format, and has a chance of being incompatible with today's libraries if they rely on things like Node.js exports.

I tried to add type:module to my app's package.json and it causes errors in Meteor 3.0 beta.0 like so:

https://forums.meteor.com/t/meteor-3-0-type-module-in-package-json-causes-error/61084

I also tried find a workaround to import native Node ES modules on the server side, but have not yet been successful:

https://forums.meteor.com/t/unable-to-import-native-es-modules-in-meteor-2-0-or-3-0-beta-0/61085

(it is easy to run client code as vanilla JS modules, that post links to an example)

[StorytellerCZ]

Agreed, this is a must for me as well as I have packages that I need to upgrade with use the Node.js exports.

[harryadel]

MS folks @fredmaiaarantes @Grubba27

I believe this discussion is long overdue for some updates on your part. Looking forward to it. 👍

[Grubba27]

Hey Harry! I'm currently working on migrating docs(and updating them to be correct with the API in v3.0). You can check the PR here (there is a todo list of what I'm doing and what is left)

Also, @denihs posted last week about our progress

[harryadel]

Thank you for clarifying things up. It's just we're kept in the dark and get a random update once every while about previously done work but no future plans. You're working on updating the docs and denis and on source map error, is that it?

⛏️👷 means someone is working on it

⛏️👷 Update Meteor API Docs to v3 and migrate to Vitepress [Grubba27]

⛏️👷 Error with Source-map showing up in some cases. Context. [denihs]

[dallman2]

@Grubba27 @harryadel @fredmaiaarantes I have looked through the backlog and the Meteor beta code, as well as the progress posts referenced above. However, I cannot really find an authoritative answer on the plan for call/ apply. Will these methods be deprecated in favor of callAsync/ applyAsync? Will they still exist in the first release of Meteor 3? As of 3.0-beta.0, they are still there and functioning.

Thanks guys

[denihs]

Hi @dallman2, in version 3, you'll still be able to use these methods normally. We don't have plans to remove them.

They will still work as they're working now in version 2, but of course, there are scenarios where you don't want to use them. For example, when calling async Methods, especially the ones that handle async stubs (Mongo methods).

[ramesh-bhatta-oohmedia]

Hello Meteor Community,

I hope this message finds you well. I am reaching out to seek assistance regarding issues I encountered after updating my Meteor project to version 3.0-beta.6.
Here's a brief overview of the situation:
I created my app using the command: meteor create --vue simple-todos-vue.
Following that, I decided to update my project to Meteor version 3.0-beta.6 using the command:
meteor update --release 3.0-beta.6.
However, post-update, I am facing a specific issue related to the 'jorgenvatle:vite-bundler' package. The error message is as follows:
javascriptCopy codeWhile loading plugin vite from package jorgenvatle:vite-bundler:
packages/modules-runtime.js:222:12: Cannot find module 'fibers'

I have attempted to troubleshoot this issue by consulting the official Meteor documentation and various online resources. Unfortunately, my efforts have not led to a resolution.

If anyone in the community has encountered a similar problem or has insights into potential solutions for the 'Cannot find module 'fibers'' issue, I would greatly appreciate your guidance.

To provide more context, I have also checked the package versions and ensured that 'fibers' is installed in my project using meteor npm install fibers. Despite these efforts, the issue persists.

If you require additional details or specific error logs, please let me know, and I will promptly provide them.
Thank you in advance for your time and support. I look forward to any insights or suggestions the community can offer.

Thanks,
Ramesh

[StorytellerCZ]

Hi @ramesh-bhatta-oohmedia, there is already an issue for this: #13057

[dallman2]

Hey all,

Are there any new version 3 betas in the pipeline? I have been seeing a lot of activity on the draft PR, but didn't catch another beta version. Should we be expecting an RC next? I am getting a little worried about the deadline for the end of security patches on Node 14 looming...

[denihs]

Hi, just wrote a quick update in our Forums about this.

We plan to release our last Beta between this week and the next. After that, we'll start working in our first RC.

[fredmaiaarantes]

I organized the discussion and added estimated release dates for the last Beta and first RC versions.

[dallman2]

Thanks for adding that. This makes it much easier for us to plan our migration timeline.

[harryadel]

Thanks for clearing things up. 👍

[dhanalakshmi3467]

account-base ui npm add throwing errors

I am currently using Meteor js version 2.15 and need to install accounts-base-ui. However, when attempting to add wiseguyeh:accounts-azure-active-directory, I encounter errors. Could you please advise on the appropriate version?

[StorytellerCZ]

Please check with the package maintainer. Given that the package had last update 10 years ago, I would recommend finding a newer version of Azure OAuth. It is unrelated to this discussion topic.

[henriquealbert]

Updates about the first Meteor 3.0 RC Release:

Due to some roadblocks, our ETA for the RC Release has been postponed to 19th April.
These are the last tasks that we are finishing:

• Sequential packages loading order [radekmie] [PR]
• Update NPM, Node and TypeScript to latest versions [nachocodoner] [PR] - a nice to have but not a blocker.

[henriquealbert]

It is time for a Weekly update 🎉 ☄️

We are proud to say that we have the first Release Candidate for Meteor 3.0 🤩🥳
You can check more details about it here.

The priority of the next RC will be to review and fix issues with Cordova's experience.

Next Releases:

• Meteor 2.16 [PR]
  • We plan to release it by the end of this week.
• Meteor 3.0 RC (next): May 3, 2024.
  • The plan is to have a new release candidate every 2 weeks.

---

You can follow the updates on What's left until an official Meteor 3.0? Discussion, and on the Release 3.0 PR.

[henriquealbert]

It is time for a Weekly update 🎉 ☄️

We are proud to say that we have the Release for 2.16 beta 🤩🥳
You can check more details about it here .

Tasks and fixes for the next Meteor 3.0 RC:

• Circle CI tests failing for external packages [Group 5]
• Meteor developer accounts do not work when logging in with github · Issue #12418
• Add missing observe async types by StorytellerCZ · Pull Request #13103
• Added waitUntilAllLoaded safety check. by radekmie · Pull Request #13102
• refactor(accounts): add ddp type to accounts-client by vit0rr · Pull Request #13042
• Make sure Vue and Svelte apps run with Meteor 3

Next Releases:

• Meteor 2.16 RC [PR]
  • We plan to release it early next week, probably Monday (May 6th).
• Meteor 3.0 RC (next): Friday, May 3rd, 2024.
  • The plan is to have a new release candidate every 2 weeks.

---

You can follow the updates on What's left until an official Meteor 3.0? Discussion, and on the Release 3.0 PR.

[henriquealbert]

It is time for a Weekly update 🎉 ☄️

We are proud to say that we have the Release for Meteor 3.0-rc.1 🤩🥳
You can check more details about it here.

We also have the Meteor 2.16-rc.0 🤩🥳
You can check more details about it here.

---

Tasks and fixes for the next 3.0 RC:

• Review the Types for WebApp/Express
• [Meteor 3] Fix handling unexpected errors during build by zodern · Pull Request #12675
• Fix and Review any places using findOne in the server
• [Meteor 3] Environment Variables resets value too early · Issue #13112
• [Meteor 3] EnvironmentVariable.withValue has different return value on client and server · Issue #13113
• Unable to create new meteor 3 projects · Issue #13106
• Make sure apollo skeleton works with Meteor 3
• Docs for all modules strict breaking change
• Review security updates

Next Releases:

• Meteor 2.16 - Official [PR]
  • We plan to release it next week. Probably until May 14th.
• Meteor 3.0 RC - next [PR]
  • Monday, May 20th, 2024.
  • The plan is to have a new release candidate every 2 weeks. Every Monday.
• Meteor 3.0 - Official
  • We need your help testing the RC versions to make it more stable before the official release.