Fibers Public Roadmap and Meteor 3.0

[awatson1978]

Wooo hoo! It runs! Excited to give this a test drive!

[superfail]

ESM, please! It’s 2024!

[denyhs]

Hello everyone!

Here is another update on what we’ve been working on in the past few weeks.

We fixed an issue where Symbol.asyncIterator on Cursor was not working. We updated the Reify package inside the core where it wasn’t updated yet. Also worked on issues like: Insert not working for collection created of the fly.

Right now, we are working on:

• Uncaught Promise Rejection when throwing stub error
• Check how difficult it would be to enable native ES modules on Meteor (We already have a plan for this. More update on it later )

We also moved forward with the docs, and it’s looking really good. Here is a sneak peek:

We are planning on releasing a Beta 1 pretty soon, so stay tuned!

You can follow the updates on our overview doc , and on this Github PR

[denyhs]

Hello everyone!

Here is one more update.

We release one more Beta, this one being beta.4.

It includes:

• The Async iterator now works (for await (const item of Collection.find()));
• OAuth is now working as it should;
• Meteor.userAsync now works in publications;
• Isomorphism in Collection is back;

We’re already working on the tasks for the next one, so stay tuned!

You can follow the updates on our overview doc , and on this Github PR.

[denyhs]

Hello everyone! If you are still not aware, a few days ago, we released our Beta 6!

You can check more about it here.

Your test and feedback is really important. See you soon!

[denyhs]

Hi y’all! Just a quick update.

We’ve been working hard to finish some tasks in the past couple of weeks, and soon (between this week and the next one), we’ll release our last Beta!

After that, we’ll start working on the first RC right away.

Right now, I’m working on this PR, which is really important as it’ll update our skeletons to work with Meteor 3.

We also have this one that we want to fix before releasing this Beta. Then we’ll be ready.

That’s it for now, see you soon!

[fredmaiaarantes]

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

[paulishca]

For those deploying to AWS Node machines (EBS) or those using AWS SDK (such as @aws-sdk/client-s3) after 1 of May, Node 14 is no longer supported. Announcing the end of support for Node.js 14.x in the AWS SDK for JavaScript (v3) | AWS Developer Tools Blog

[rjdavid]

@paulishca

For those deploying to AWS Node machines (EBS)

I did not find any related announcement about deployment to AWS being affected by the drop of support of Node 14 from AWS SDK for JS V3.

P.S. This just reminded me that I need to move a number of projects from AWS SDK V2 to V3

[paulishca]

I get the notification in Meteor 2.x projects where the SDK is installed.

I tried to deploy a Node 14 on a Node 20 machine and it didn’t work. Node 14 cannot be selected any more. If you have a new project it is possible that it cannot be deployed (although the bundle packs its own Node 14). If I remember right, I had problems related to node-gyp. I would assume the Node 14 AMI still exists after 1st of May and new machines can be started in the same autoscaling group.

In the worst case scenario, I believe deployments can be done on custom AMIs.

[rjdavid]

Node 14 is available until September 30, 2024, according to this page:

Elastic Beanstalk platform versions scheduled for retirement - AWS Elastic...

[marklynch]

We have Meteor (and node 14) running on EB instances that come with Node 18. I don’t think the underlying installed version matters - as Meteor then runs it’s own bundled one.

[rjdavid]

@marklynch

as Meteor then runs it’s own bundled one

How are you deploying to production? Did you mean that you are running the meteor tool in production (with the bundled node version)?

We do not run “meteor” nor the “bundled node version” in production. But our custom AMI uses the meteor team’s forked node version. Some folks might be ok with the provided AMI by AWS

[marklynch]

@rjdavid

How are you deploying to production? Did you mean that you are running the meteor tool in production (with the bundled node version)?

We use mup and the EB plugin.

@rjdavid

We do not run “meteor” nor the “bundled node version” in production. But our custom AMI uses the meteor team’s forked node version. Some folks might be ok with the provided AMI by AWS

mup will use nvm to install the version of node required by meteor - so the version bundled with the AMI isn’t important.

[paulishca]

AFAIR the problem with deploying Meteor 2.15 on a Node 20 machine in EBS was related to Python and the compilation of/by pre-gyp/node-gyp which I think is used/necessary by bcrypt.

[hschmaiske]

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 tasks for the first RC:

• Fix issue with audit-argument-checks after changes on env contexts [nachocodoner] [PR]
• Fix promise rejection throwing several times [nachocodoner] [PR]
• Support Linux ARM with the Meteor installer [nachocodoner] [PR]
• Fix checks [nachocodoner] [PR]
• Sequential packages loading order [radekmie] [PR]
• Update NPM, Node and TypeScript to latest versions [nachocodoner] [PR]
• Update apollo skeleton to use async [StorytellerCZ] [PR]

Estimated Release Dates

• Last Meteor 3.0 Beta: March 26, 2024 - meteor update --release 3.0-beta.7
• First Meteor 3.0 RC: April 19, 2024
• Meteor 2.16: We plan to start working on a release after the first RC

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

[hschmaiske]

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.

[hschmaiske]

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.

[vikr00001]

Can this be included in the next RC candidate?

Meteor 3 - "Meteor.userId can only be invoked in method calls or publications."?

Thanks for reporting this. I’ll try to simulate it and see what’s happening.

[hschmaiske]

Yes, it will be included in RC.2!