I cloned the github repo,
commented out the line api.versionsFrom(['2.8.0'])
and changed the line
api.use(['blaze@2.7.1'], 'client', { weak: true })
to
api.use(['blaze@3.0.0-alpha300.17'], 'client', { weak: true })
and it works, thanks
I cloned the github repo,
commented out the line api.versionsFrom(['2.8.0'])
and changed the line
api.use(['blaze@2.7.1'], 'client', { weak: true })
to
api.use(['blaze@3.0.0-alpha300.17'], 'client', { weak: true })
and it works, thanks
We’ll be releasing a beta version soonish which will resolve these issues.
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:
meteor update --release 3.0-beta.7
You can follow the updates on What’s left until an official Meteor 3.0? Discussion, and on the Release 3.0 PR.
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.
You can follow the updates on What’s left until an official Meteor 3.0? Discussion, and on the Release 3.0 PR.
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:
waitUntilAllLoaded
safety check. by radekmie · Pull Request #13102You can follow the updates on What’s left until an official Meteor 3.0? Discussion, and on the Release 3.0 PR.
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:
It is time for a Weekly update
We are proud to say that we have the Release for Meteor 2.16 official
You can check more details about it here.
It’s time for a weekly update
It’s been some time, but we are proud to say that we have the Release for Meteor 3.0-rc.2
You can check here for more details.
Tasks and fixes for the next, and final until the official, Meteor 3.0 Release Candidate (rc.3):
Meteor 3-rc.3
is expected to arrive on Tuesday, June 11th, stay tuned.
These dates are subject to change as we add or remove things from the backlog.
It’s time for a weekly update
We are proud to say that we have the Release for Meteor 3.0-rc.4
You can check here for more details.
Tasks and fixes for the next, and official, Meteor 3.0 Release:
addEmailAsync
aliasMeteor 3.0 is expected to arrive on Tuesday, July 8th, stay tuned.
These dates are subject to change as we add or remove things from the backlog.
Weekly Update June 28th, 2024
So far we have released rc4
as we mentioned in our previous updates, and work is progressing well for our official Meteor 3 release.
You can check here for more details about our last Release Candidate.
The backlog has evolved a little over the last days with some issues gaining priority, our most important ones are as follows:
meteor-tool
is missing, this has gone up in priority but it’s extremely hard to solve, we have a path forward but have some loose ends we need to account for, some tests on Windows are failing at the moment@vlasky/whomst
since it depends on a package called posix
which builds a binary and breaks on some installationsWe also confirmed that Cordova is working completely fine, this was done by @nachocodoner, one of our developers with the most expertise in that area.
We are also revamping the documentation and researching ways to simplify the mechanics for call
and callAsync
, we have @denyhs at this forefront and also huge help from @zodern . The goal is to make Meteor have the best Developer Experience as possible and the migration as simple as possible too.
Other tasks and fixes for the next, and official, Meteor 3.0 Release:
addEmailAsync
aliasasyncLocalStorage
globaltinytest
major version increaseMeteor 3.0 is expected to arrive on Monday, July 8th or 15th at the most
Next Releases
These dates are subject to change as we add or remove things from the backlog.
Weekly Update July 5th, 2024
So far we have released rc4
as we mentioned in our previous updates, and work continues progressing well for our Meteor 3 official release.
You can check here for more details about our last Release Candidate.
We have launched our Meteor Lounge Discord server, you read more about it here.
Today we have successfully hosted our first Community Call where many amazing people joined like @storyteller @copleykj, to name just a few! We are going to host these regularly, the time is still to be defined. If you have any suggestions please reply below.
Tasks and fixes for the next, and official, Meteor 3.0 Release:
posix
packagecallAsync
addEmailAsync
aliasmeteor create my-react-app
due to skeleton cloneMeteor 3.0 is expected to arrive from Monday, July 8th to July 15th at the most. Most likely sometime mid-week.
Next Releases
These dates are subject to change as we add or remove things from the backlog.
Hi Cloudiy,
The error message you shared shows you that simple:rest 1.2.1 requires accounts-base-2.1.0, which is a version that is not compatible with meteor 3.0.
In order to fix this issue, you either need to update the package manually yourself, request an update to the package on github, but as you can see the development of this package has stopped, so alternatively I would recommend looking for an alternative or determining if you really need this package in your project and remove it.
Let me know if this helps and if you are able to upgrade!
also note, that simple:rest might not be required anymore since 3.0 uses express which basically provides all the functionality natively unless I missed a detail here.
simple:rest package automatically exposes your methods, publications and collections as rest endpoints. That’s not available as of now with the move to express.
You might be talking about a different package
Yes, we have projects running in production with Meteor 3 and Langchain
Since 3.0.1 was the public release, I’m wondering if the schedule for 3.0.2 has moved forward at all? We’re eagerly awaiting 3.0.2 as I think this issue is a blocker for us to roll out Meteor 3 in production (it is I think what is underlying some weird behavior that is causing UX issues in our app).
The issue mentioned is already fixed in our release branch, we are planning to release 3.0.2 as soon as we can, waiting on other fixes to include in it. I would say Thursday/Friday.