Yes, the issue I was getting with the source map was fixed in the first beta.
So we have a project running in production with Meteor 3 without any changes in Meteor core.
Yes, the issue I was getting with the source map was fixed in the first beta.
So we have a project running in production with Meteor 3 without any changes in Meteor core.
Thanks a lot. Went back to it and gave it another try and it works. I am live with one Meteor 3. This opens doors to some testing.
I’d be interested in hearing about how you integrate to LLM if that is possible.
Mostly via langchain.js, which requires Node v18. Once we were able to run Meteor on Node 18, everything mostly fell into place and it was basic app developing using an external API. Given langchain’s predominance in the LLM space, I suspect Meteor v3 is going to be remembered as the version where AI/LLM support was added.
I just tried to create an application with FlowRouter and blaze in beta 3.0, but it doesn’t seem to work yet, has anyone tried it yet?
Likely, it is pulling an old version of FlowRouter and possibly an old BlazeLayout version also. For the latter, and other few packages, see my post here Looking for help migrating packages to Meteor 3.0 - #29 by illustreets. They all have pull requests submitted, you might want to clone locally those PRs until the maintainers merge them.
We should be able to help more if you paste the log here.
Hello,
I have just tried.
Make sure you use :
ostrio:flow-router-extra@3.10.0
Then you have to clone the package and remove this line :
api.versionsFrom(['1.4', '3.0-beta.0']);
And it works
Thank you both for your answers.
Me again
Has anyone already made alanning:roles work?
is there a newer version than 3.6.2?
No 3.6.2 is the latest one. There will be v4, which will remove sync api from the server. Other than that 3.6.2 is compatible with Meteor 3.
Ok but…
So why do I get these errors when I try to update?
error: Conflict: Constraint accounts-base@2.2.4 is not satisfied by accounts-base 3.0.0-beta300.6.
Constraints on package “accounts-base”:
Conflict: Constraint mongo@1.16.0 is not satisfied by mongo 2.0.0-beta300.6.
Constraints on package “mongo”:
Conflict: Constraint blaze@2.7.1 is not satisfied by blaze 3.0.0-alpha300.17.
Constraints on package “blaze”:
When you update and there’s conflicts you can use the exclamation prefix like so: alanning:roles@3.6.2! in .packages
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.