There is very high chance you need to update that package to make it works with new async api.
Another week, another update. We are still working on the past week’s tasks and progressing on them.
Currently, we are actively working on the following tasks:
-
Make sure all the tests (packages/tools) are passing in our CLI - this is the main bottleneck. It has many tests, which are very complex to solve.
– Groups 0, 1, 2, 4, 5, 6, 7, 9, 10, and 11 are done - missing only Groups 3, 8, and Isolated Tests that we are going to work on this week.
You can follow the updates on our Fibers Public Roadmap and on this Github PR
Another week, another update. Here are the latest updates on the successfully completed tasks:
Currently, we are actively working on the following tasks:
- Update changelog for Alpha.0
- Update release 3.0 with devel(2.12 release)
- Review all env variables (DISABLE_FIBERS etc)
After finishing those tasks, we are moving forward to release the first Alpha of Meteor 3.0.
You can follow the updates on our Fibers Public Roadmap and on this Github PR
Hey people, just a quick update:
Our team is currently transitioning from using Favro to GitHub Projects. This move will allow us to have all our MeteorJS-related information in one location, making it easier for everyone to access and keep track of the status of the Fibers Public Roadmap.
Here is the link to Fibers Public Roadmap
Regarding the latest tasks updates, we are releasing Meteor 3.0 Alpha. We are currently addressing some issues related to the version bump, and we aim to release the Alpha as soon as possible. Rest assured, I will keep you informed of any further developments.
So Meteor 3.0 is all about Fibers?
Just asked AI about it: “… keep in mind that the actual use of fibers can get much more complex, especially when error handling and more complex control flows are involved. Furthermore, the fibers
package is not the recommended way of handling asynchronous operations in modern JavaScript. Promises and async/await syntax provide a much more robust and easier-to-understand method of handling async operations and are generally recommended for most use cases.”
We are transitioning from Fibers due to its lack of support in Node.js versions beyond 14. As we move forward, we’re targeting Node.js v18 for Meteor 3.0 and plan to upgrade to Node.js v20. While we’ll be implementing numerous improvements, the primary distinction between Meteor 2.x and Meteor 3.0 will be the adoption of async/await syntax and the removal of Fibers.
You can read more about it here: Change how Meteor executes Async code · meteor/meteor · Discussion #11505 · GitHub
Thanks, relieved to hear it’s in line with best practices.
Good news - Meteor 3.0 is about moving off of fibers, to promises and async/await.
Hey people, quick weekly update:
Here are the latest updates on the successfully completed tasks:
-
Released Meteor 3.0 alpha - you can try it in a new app by running
meteor update —release 3.0-alpha.6
- Review all env variables (DISABLE_FIBERS etc)
- Update changelog for Alpha
- Update release 3.0 with devel(2.12 release)
- Create new dev bundle
- Bump all packages related to Fibers
- Bump release 3.0 dev-bundle
Currently, we are actively working on the following tasks:
- Review Meteor.call, Meteor.callAsync, Meteor.apply, Meteor.applyAsync
- Review Cordova Commands
- Blaze support async
- Review Profile.time()
You can follow the updates on our Fibers Public Roadmap and on this Github PR
Congrats to the team for releasing the alpha version.
What’s the best way to view the Changelog or any guide for us to test?
Congrats to the team for the Alpha release.
As an engineer, seeing a team successfully update such a complex codebase is inspiring. Looking forward to more success in the future.
Currently, we are in the process of creating a guide for the beta version. However, in the meantime, the changelog can be found on GitHub. meteor/3.0.md at 6bc3d8f665d64e8f5ca3a07e3ada3091ccd2b064 · meteor/meteor · GitHub or here
Hey people, quick weekly update:
Here are the latest updates on the successfully completed tasks:
Currently, we are actively working on the following tasks:
- Review Meteor.call, Meteor.callAsync, Meteor.apply, Meteor.applyAsync
- Review Cordova Commands
- Fix packages tests branch release-3.0
- Wrapping up with: Support top-level await in Reify
Our team is working hard to release the new Alpha version as quickly as we can. However, we are facing some challenges with the CI failing tests, which is slowing down our progress. But rest assured that we are actively working to resolve this issue. Thank you for your patience and understanding.
You can follow the updates on our Fibers Public Roadmap and on this Github PR
Also big congrats from everyone at Orderlion to the whole Meteor team!
Really awesome that you are tackling this huge endeavour and making awesome progress!
Keep it coming!
Hey people, quick weekly update:
Here are the latest updates on the successfully completed tasks:
- Review Cordova Commands
- Release Meteor 2.13 beta
- Wrapping up with: Support top-level await in Reify
Currently, we are actively working on the following tasks:
- Review Meteor.call, Meteor.callAsync, Meteor.apply, Meteor.applyAsync - we are blocked on this one because the CI is failing
- Fix packages tests branch release-3.0
- Fix CI for Tools
- Run Meteor commands on Node v18
Our team is working hard to release the new Alpha version as quickly as we can. However, we are facing some challenges with the CI failing tests, which is slowing down our progress.
Thank you for your patience and understanding.
You can follow the updates on our Fibers Public Roadmap and on this Github PR
Hey people, quick weekly update:
Here are the latest updates on the successfully completed tasks:
- We fixed a bunch of packages tests (1100/1500)
- Release Meteor 2.13 RC
- Preparing new PRs for Meteor 2.13
- Support top-level await in Reify
- Review Meteor.call, Meteor.callAsync, Meteor.apply, Meteor.applyAsync - We have a draft PR here and we need more input from the Community about it.
Currently, we are actively working on the following tasks:
- Fix packages tests branch release-3.0 (1100/1500)
- Fix CI for Tools - missing one flaky test.
- Run Meteor commands on Node v18 - we’ve made some progress here, and when we get it running on Node v18, we’ll target Node v20.
- Review Changelog
Our team is working hard to release the new Alpha version as quickly as we can. We are almost there
Special thanks to Rodrigo Nascimento from Rocket.chat for assisting us with some tests.
You can follow the updates on our Fibers Public Roadmap and on this Github PR
Fantastic. This is one of our major blockers for migration.
Hi I tried meteor update —release 3.0-alpha.6
but node version behind it is still 14.21.3
which ended life in April this year. Is there any plan or other release that allows using meteor with newr node? Many packages are not usable in meteor anymore due to this.