My day job is google integrations and tactical scripts with Appscript and Javascript.
As a result my time is not focused on full stack. Meteor and Blaze are the fastest way to spin up a solution that requires a reactive front end and a data backend, without me having to keep up-to-date with 15 frameworks I might need if I was full stack developing without it.
I was reluctant to use it whilst it was using a non supported Node version for liability reasons.
I am converting my app to 3.0. Since 3.0 was in a rc phase, I thought it was close enough that I could finish the migration. However I’m finding a few community packages are still not 3.0 compatible (Though they do have in-progress PR’s), which is going to block a 3.0 migration. Do you know where on the roadmap it would be to make sure community packages are 3.0 compatible? If not by the time 3.0 releases?
I did trim the fat in my app and removed/replaced several unmaintained packages, but with community packages I’m not sure I should do that.
I’ve been upgrading my app from 2.7.3 all the way to 2.16 with success at each version. Very happy!
Now, I’m trying to test out:
meteor update --release 3.0-rc.1
but I hit this error every time - for a couple of days now:
Unable to update package catalog (are you offline?)
If you are using Meteor behind a proxy, set HTTP_PROXY and HTTPS_PROXY environment variables or see this page for more details:
https://github.com/meteor/meteor/wiki/Using-Meteor-behind-a-proxy
=> Errors while initializing project:
While selecting package versions:
error: Conflict: Constraint blaze@2.0.3 is not satisfied by blaze 3.0.0-alpha300.17.
Constraints on package "blaze":
* blaze@3.0.0-alpha300.17 <- launch-screen 2.0.1-rc300.1 <- mobile-experience 1.1.2-rc300.1
* blaze@3.0.0-alpha300.17 <- blaze-html-templates 3.0.0-alpha300.17
* blaze@3.0.0-alpha300.17 <- spacebars 2.0.0-alpha300.17 <- templating-runtime 2.0.0-alpha300.17 <- templating 1.4.4-alpha300.17 <- blaze-html-templates 3.0.0-alpha300.17
* blaze@3.0.0-alpha300.17 <- templating-runtime 2.0.0-alpha300.17 <- templating 1.4.4-alpha300.17 <- blaze-html-templates 3.0.0-alpha300.17
* blaze@2.0.3 <- kadira:blaze-layout 2.0.1
* blaze@3.0.0-alpha300.17 <- accounts-base 3.0.0-rc300.1
Do I have to update Blaze separately perhaps?
I have an npm package that requires node >= 18, but Meteor 2.16 is still on node 14.21.4
I am using GitHub - mikeborozdin/http-streaming-request exactly as described in it’s readme (to talk to OpenAi, but for me, Ollama installed locally) and it is exactly what I need.
Or will the upgrade to Meteor 3.0-rc.1 be better tried if I try to upgrade from an earlier version, rather than where I am currently with 2.16?
I suppose I could wrangle my own version of the streaming-request npm package, but …
Any ideas, anyone?
Blaze Layout is just a peer dependency of kadira:flow-router. Maybe you go switch to ostrio:flow-router-extra to drop kadira:blaze-layout. The ostrio router also enables yielding render targets.
I already had the ostrio:flow-router-extra package installed.
I removed the kadira:blaze-layout package.
Then, I had to change BlazeLayout.render(… to this.render(… in the action() function of FlowRouter routes, but that now gives me a this.render is not a function error message.
I wrote a whole screed of code outlining my problems, but I’ll stop here and create another thread.