We badly need this to join the testing of alpha/beta
Hello people, quick bi-weekly update:
Here are the latest updates on the successfully completed tasks:
-
Meteor 3 Alpha - We now have a final alpha version for Meteor 3.0 running with Node 18 To test this version you can, for example, create a new app like this
meteor create --release 3.0-alpha.11 test-alpha-11
, or update an existing app with this commandmeteor update --release 3.0-alpha.11
.
Currently, we are actively working on the following tasks:
We officially start to work on the first Beta version
-
Update NPM to version 9 - Right now we have Meteor 3.0-alpha.11 with Npm 8. There were some issues when we tried to update directly to version 9.
-
More will be started in the next few days
You can follow the updates on our Fibers Public Roadmap and on this Github PR
Hi guys, one more thing here. We already have an image that we can use to deploy your apps on Galaxy with this Alpha version.
We still haven’t set it as the default, so if you want to deploy it to Galaxy, you can add this to your settings:
{
"galaxy.meteor.com": {
"baseImage": {
"repository": "meteor/galaxy-app",
"tag": "20230831T140772Z_29ad488"
}
}
}
Great , this version of Meteor comes at the right time with one of my projects which needs a recent version of node to run “puppeteer-stream”, I managed to create the app I needed, thanks!
Anyone know a docker image to deploy this alpha with mup?
All our images are available as well for 3.0-alpha.11
I believe our images are compatible with Mup.
If you have questions, feel free to send them to support@zcloud.ws
Hi, I just published a new topic about Performance tests on Meteor 3.
Please take a look and choose how you prefer to consume the results: Performance tests between Meteor 3 & Meteor 2 - Help on format
Thank you very much @filipenevola this image works!
‘zcloudws/meteor-node-mongodb-runtime:3.0-alpha.11-with-tools’
Hello people, quick bi-weekly update:
Here are the latest updates on the successfully completed tasks:
- Update NPM to version 9 - We have successfully updated NPM to version 9 This will be available in the next 3.0 release.
Currently, we are actively working on the following tasks:
- Release a new Beta version - We will focus on delivering the first Beta version for the next two weeks. This version will include:
- Update NPM to version 9
- Review major/minor version of packages - A few days ago, we had discussions in the Slack community about how bumping core packages, that didn’t have a breaking change, to a new major version wasn’t a good idea because this is now making harder to update an app from version 2 to 3. So, we will review every package and revert this change to packages that don’t need a bump.
- More will be started in the next few days
You can follow the updates on our Fibers Public Roadmap and on this Github PR
The link copy suggests that this has not been successfully migrated to npm 9 (“Right now we have Meteor at version 3.0-alpha.11 with Node 18 and Npm 8”). Does that need to be updated or is it correct?
I think the task status is done is what @denyhs wanted to highlight with the link.
Great work folks, really excited for this.
ah! Got it So focused on copy I did not notice the status checkmark.
At the moment, we have the latest alpha with Node 18 and Npm 8
We just finished the update to npm 9, and we will release a new alpha version to include these changes.
Thanks for clearing it up. I’m trying to figure out what to report this week on MeteorJS Dispatches. That is, looking for what the build will be that they can download. Expecting 3.0-alpha.13 or something similar…
I appreciate all the work that everyone in the core team is doing to handle the release of Meteor 3.0. At the same time, I love the loyalty and commited community based on the love for the tool. The open to speech and proactive spirit define us on our endevors to keep using Meteor in our daily basis, whether it’s in the form of personal usage or through invaluable contributions such as packages and enhancements. We should not lose the focus on that no matter which are the circumstances and reactions around us.
I am excited and motivated on Meteor 3. I started to use it locally. In fact, I wish go further and start provinding some adaption to community packages, to not use fibers anymore.
I created a small app using Meteor 3, and I realized that tests are not working properly. We are missing the adaption of test packages there. Tests are an essential part to adapt the rest of packages, since almost all them involve to run tests to verify the behaviors are still working.
I did some changes on test packages to be fiber-free and I was able to pass properly the tests for an example app as you can see in the picture below.
I am not sure if it will cover all scenarios. Surely, there is more to adapt, like test coverage and may others, this is just a start. But the simple test capability may be adapted with a minor change I could commit for review.
My questions are:
- Is anyone already in charge of the testing part? Is it planned or already tackled by the core or any community member?
- How would the procedure be to start contributing with the changes on the packages?
I believe these are the next steps to define in order to get more people involved on this migration.
It is part of the Beta Roadmap: Fibers Public Roadmap - Meteor 3.0 · GitHub
@hschmaiske might give a better answer on this
As rjdavid said, it’s part of the roadmap, but you could definitely help.
Even if you don’t have everything ready right away, you can open a draft PR against this branch with a detailed description of what you’re doing and a checklist of what’s missing.
If you need any help, you can also DM me on Slack.
Hello everyone, quick bi-weekly update:
Here are the latest updates on the successfully completed tasks:
- New alpha version - You can create a new app with this version by running
meteor create --release 3.0-alpha.15 myapp
- Review major/minor version of packages - we reviewed all the packages and rolled back the versions that didn’t need to be updated.
Currently, we are actively working on the following tasks:
- Fix problems with our tutorials when doing them with Meteor 3 - we’re extensively testing our Alpha version right now to make sure we can refine it more before a Beta version. We already found simple bugs, like
Cursor.count()
not working properly. So we want to tackle those types of bugs first before releasing a Beta. - More will be started in the next few days
You can follow the updates on our Fibers Public Roadmap and on this Github PR
I heard that in Meteor 3.0, we will use express
server and remove connect
package. Is that right?
That’s right @minhna! If you have any concerns, there is a topic with some discussion around it.
Hello everyone! Here is a small update:
Some tasks we’ve been working on it:
- Fix problems with our tutorials when doing them with Meteor 3: We worked on this from different PRs: #12802, #12808.
- Unhandled Rejection when fails to bundle the app: We found this problem while working on the above issue. It goes deeper than we thought, and we continue to investigate the root of this problem.
Our plan for the next week is to release one more Alpha, which will include changes like this one and this one.
After that, we’ll address the issue Unhandled Rejection when fails to bundle the app as well as more issues our community is reporting, like this one.
See you soon for more updates!
You can follow the updates on our Fibers Public Roadmap and on this Github PR .