We are excited to announce the release of the “Fibers Public Roadmap,” an initiative designed to improve communication and transparency between Meteor Software and our valued community members.
As many of you know, Meteor has always been committed to building the best possible platform for web and mobile app development. However, we recognize that there is always room for improvement, and that’s why we’re launching this new roadmap.
This Roadmap will serve as a central hub for all updates related to our development efforts. It will include information about what we are working on regarding the Fibers migration, as well as our progress on each of these items. With this roadmap, we hope to provide our community with a better understanding of what we’re working on and what you can expect from Meteor in the near future.
We also have the desire to launch an Alpha version of Meteor 3.0 in the first quarter of 2023.
We understand that communication is key to building a strong and active community, and we believe this Roadmap will help us achieve this goal. We encourage you to check back often for updates, and to share your thoughts and feedback with us through our official channels.
Thank you for your continued support of Meteor, and we look forward to building an even better platform together.
We are excited to inform you that we have made significant progress on the Fibers Migration, and our target is to release Meteor 3.0 Alpha as soon as possible. Our team has been working tirelessly to ensure a seamless transition.
We are pleased to share that we have completed the following tasks successfully:
Migrated Tools commands to Async
Fixed missing files while copying node modules to rebuild native dependencies
Resolved missing globals and packages that were unable to import from the app’s node_modules
Implemented a partial fix for stylesheets
Improved error handling using TLA*
Furthermore, we are currently working on the following tasks:
Using find async on the server side using suspense for React packages
Fixing static files on the client (tools/bundle) - WebApp & TLA*
Reviewing Mongo changes
Implementing TLA* on Meteor and Reify
Fixing the accounts-password package
Adjustments to detect if fibers are enabled
Our team is optimistic about the progress we have made so far and our goal to release Meteor 3.0 Alpha. We sincerely appreciate your patience and support as we continue to work on this important project.
You can follow the updates on our Fibers Public Roadmap and on this Github PR
Great news! We are pleased to report significant progress in the Fibers Migration. Our dedicated team has been working diligently to achieve our goal of releasing Meteor 3.0 Alpha at the earliest opportunity.
We’d like to share with you the latest updates on the tasks that were accomplished, which are outlined below.
Progressed on the task “accounts-password: Meteor.user() doesn’t return the user inside a Meteor.createUser() anymore” from last week to today. Even though the task encountered a temporary block, we explained in a comment on Favro.
Wonderful news! We are thrilled to announce that the Fibers Migration is making remarkable strides. Thanks to our committed team, we have been making tremendous progress toward our goal of releasing Meteor 3.0 Alpha ASAP.
We are excited to provide you with the latest updates on the tasks that have been successfully completed, as outlined below.
Question that i can’t seem to resolve from reading: Are the sync versions of the minimongo find, update etc. going to stay or are they also being replaced by async api only? In our codebase we have a lot of templates that require sync syntax. I understand that isomorphic methods must be async, but in the views, sync versions of find and findOne are possible and would be hugely helpful for us in the migration process. Not only would we need to rewrite all view helpers but for angularjs it would mean we couldn’t use method calls in templates for getting data which would mean a massive rewrite. Please keep a sync version
Another week, another update. Here are the latest updates on the successfully completed tasks, showcasing our commitment to delivering a high-quality product:
Tested Simple Tasks using meteor3 (it worked in parts)
Work dividing workloads for the Blaze async task with the help of the community - callout link
This last week, we started working on Blaze in this PR. You can already see the letAwait syntax working in unwrapping promises. It still misses having pending and error states.
One question: You mention that you had to take special care for accounts-password. Does that mean that most other accounts packages will have to be adjusted, too? For instance, we’re using the social login packages including Quave’s accounts-apple.
I’ll keep doing these weekly updates, even if we get stuck on something.