Hey everyone!

This is Gabs Ferreira, lead developer advocate at Meteor Software.

Most of you may not know, but Meteor.js is more alive than ever! We just released version 3.1 with major infra improvements and a some other good stuff: https://blog.meteor.com/meteor-js-3-1-a-new-dawn-for-full-stack-javascript-development-fe54c372c314

There's a lot going on here (including a complete rebranding), and I hope you consider giving Meteor a try again :)

Trying toi upgrade an app,

I can't go any higher than this:

aldeed:collection2@4.0.3
aldeed:simple-schema@2.0.0
allow-deny@2.0.0
autoupdate@2.0.0
babel-compiler@7.11.1
babel-runtime@1.5.2
base64@1.0.13
binary-heap@1.0.12
boilerplate-generator@2.0.0
caching-compiler@2.0.1
callback-hook@1.6.0
check@1.4.4
core-runtime@1.0.0
dburles:collection-helpers@1.0.0
ddp@1.4.2
ddp-client@3.0.2
ddp-common@1.4.4
ddp-server@3.0.2
diff-sequence@1.1.3
dynamic-import@0.7.4
ecmascript@0.16.9
ecmascript-runtime@0.8.3
ecmascript-runtime-client@0.12.2
ecmascript-runtime-server@0.11.1
ejson@1.1.4
es5-shim@4.8.1
facts-base@1.0.2
fetch@0.1.5
geojson-utils@1.0.12
hot-code-push@1.0.5
hot-module-replacement@0.5.4
id-map@1.2.0
inter-process-messaging@0.1.2
launch-screen@2.0.1
logging@1.3.5
mdg:validated-method@1.3.0
meteor@2.0.1
meteor-base@1.5.2
minifier-css@2.0.0
minifier-js@3.0.0
minimongo@2.0.1
mobile-experience@1.1.2
mobile-status-bar@1.1.1
modern-browsers@0.1.11
modules@0.20.2
modules-runtime@0.13.2
modules-runtime-hot@0.14.3
mongo@2.0.2
mongo-decimal@0.1.4
mongo-dev-server@1.1.1
mongo-id@1.0.9
mongo-livedata@1.0.13
npm-mongo@4.17.4
ordered-dict@1.2.0
promise@1.0.0
raix:eventemitter@1.0.0
random@1.2.2
react-fast-refresh@0.2.9
react-meteor-data@3.0.2
reactive-var@1.0.13
reload@1.3.2
retry@1.1.1
routepolicy@1.1.2
shell-server@0.6.0
socket-stream-client@0.5.3
standard-minifier-css@1.9.3
standard-minifier-js@3.0.0
static-html@1.4.0
static-html-tools@1.0.0
tracker@1.3.4
typescript@5.4.3
udondan:bulk-collection-update@0.2.0
underscore@1.6.4
webapp@2.0.3
webapp-hashing@1.1.2aldeed:collection2@4.0.3
aldeed:simple-schema@2.0.0
allow-deny@2.0.0
autoupdate@2.0.0
babel-compiler@7.11.1
babel-runtime@1.5.2
base64@1.0.13
binary-heap@1.0.12
boilerplate-generator@2.0.0
caching-compiler@2.0.1
callback-hook@1.6.0
check@1.4.4
core-runtime@1.0.0
dburles:collection-helpers@1.0.0
ddp@1.4.2
ddp-client@3.0.2
ddp-common@1.4.4
ddp-server@3.0.2
diff-sequence@1.1.3
dynamic-import@0.7.4
ecmascript@0.16.9
ecmascript-runtime@0.8.3
ecmascript-runtime-client@0.12.2
ecmascript-runtime-server@0.11.1
ejson@1.1.4
es5-shim@4.8.1
facts-base@1.0.2
fetch@0.1.5
geojson-utils@1.0.12
hot-code-push@1.0.5
hot-module-replacement@0.5.4
id-map@1.2.0
inter-process-messaging@0.1.2
launch-screen@2.0.1
logging@1.3.5
mdg:validated-method@1.3.0
meteor@2.0.1
meteor-base@1.5.2
minifier-css@2.0.0
minifier-js@3.0.0
minimongo@2.0.1
mobile-experience@1.1.2
mobile-status-bar@1.1.1
modern-browsers@0.1.11
modules@0.20.2
modules-runtime@0.13.2
modules-runtime-hot@0.14.3
mongo@2.0.2
mongo-decimal@0.1.4
mongo-dev-server@1.1.1
mongo-id@1.0.9
mongo-livedata@1.0.13
npm-mongo@4.17.4
ordered-dict@1.2.0
promise@1.0.0
raix:eventemitter@1.0.0
random@1.2.2
react-fast-refresh@0.2.9
react-meteor-data@3.0.2
reactive-var@1.0.13
reload@1.3.2
retry@1.1.1
routepolicy@1.1.2
shell-server@0.6.0
socket-stream-client@0.5.3
standard-minifier-css@1.9.3
standard-minifier-js@3.0.0
static-html@1.4.0
static-html-tools@1.0.0
tracker@1.3.4
typescript@5.4.3
udondan:bulk-collection-update@0.2.0
underscore@1.6.4
webapp@2.0.3
webapp-hashing@1.1.2

Yet it complains about installing fibers no matter how I try this,

so it must be related to some packeages holgin my meteor version to meteor@2.0.1...

How to identifyu the issue?

regards,

I use the Account package and the User collection to have basic login functionality, etc. I notice that I am logged in on my test instance whenever I start Meteor for development.

• Does Meteor have already basic cookies built in?

• When I move to a real deployment in the future, will the login cookies stay, or will it be lost and I will have to use something like meteor-cookies?

In the latest 2.15 version of meteor.js, does the find().count() still bring back all documents and count them, or does it do the count in MongoDB? I was using RawColleciton to make this count faster. Just wondering if I still need to do that.

My company has a software product that is based on an older version of Meteor. To try to update any component breaks several others and has us at a standstill. Do folks here think we’d be better off rebuilding the whole app in a newer framework, or going through the effort of updating meteor and all the components to the latest meteor version? The app is attached to MongoDB Atlas on the backend and is launched on AWS App launcher. It has report generation, mapping with real time updates, data generation, and user group authentication - to give a sense of the scope.
I’m not a meteor dev myself, but I manage the project and it’s been hard to find devs who know meteor to do any fixes.

Hi guys, we needed to duplicate a legacy meteorJS app recently, onto a new server and a new database.

So we cloned the server, created a new database and pointed the cloned server to the new database.

The meteorJS app works, everything appears fine.

However we noticed that the logs is showing error like MongoError: no primary server available, everytime when restarting:

2024-02-01T06:37:06.151478+00:00 heroku[web.1]: Restarting
2024-02-01T06:37:06.217824+00:00 heroku[web.1]: State changed from up to starting
2024-02-01T06:37:06.969254+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2024-02-01T06:37:07.074219+00:00 heroku[web.1]: Process exited with status 143
2024-02-01T06:37:45.658856+00:00 heroku[web.1]: Starting process with command `.meteor/heroku_build/bin/node $NODEJS_PARAMS .meteor/heroku_build/app/main.js`
2024-02-01T06:38:00.149936+00:00 app[web.1]: Got exception while polling query MongoError: no primary server available
2024-02-01T06:38:00.149991+00:00 app[web.1]:     at ReplSetState.pickServer (/app/.meteor/heroku_build/app/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/topologies/replset_state.js:780:12)
2024-02-01T06:38:00.149991+00:00 app[web.1]:     at Timeout._selectServer [as _onTimeout] (/app/.meteor/heroku_build/app/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/topologies/replset.js:1142:43)
2024-02-01T06:38:00.149992+00:00 app[web.1]:     at listOnTimeout (internal/timers.js:549:17)
2024-02-01T06:38:00.149992+00:00 app[web.1]:     at processTimers (internal/timers.js:492:7)
2024-02-01T06:38:00.149993+00:00 app[web.1]:  => awaited here:
2024-02-01T06:38:00.149993+00:00 app[web.1]:     at Function.Promise.await (/app/.meteor/heroku_build/app/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)
2024-02-01T06:38:00.149994+00:00 app[web.1]:     at packages/mongo/mongo_driver.js:1073:14
2024-02-01T06:38:00.149994+00:00 app[web.1]:     at /app/.meteor/heroku_build/app/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40
2024-02-01T06:38:00.149994+00:00 app[web.1]:  => awaited here:
2024-02-01T06:38:00.149995+00:00 app[web.1]:     at Promise.await (/app/.meteor/heroku_build/app/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:60:12)
2024-02-01T06:38:00.149995+00:00 app[web.1]:     at SynchronousCursor._nextObject (packages/mongo/mongo_driver.js:1122:38)
2024-02-01T06:38:00.149995+00:00 app[web.1]:     at SynchronousCursor.forEach (packages/mongo/mongo_driver.js:1136:22)
2024-02-01T06:38:00.149995+00:00 app[web.1]:     at Cursor.<computed> [as forEach] (packages/mongo/mongo_driver.js:918:44)
2024-02-01T06:38:00.149996+00:00 app[web.1]:     at OplogObserveDriver._runQuery (packages/mongo/oplog_observe_driver.js:729:16)
2024-02-01T06:38:00.149996+00:00 app[web.1]:     at OplogObserveDriver._runInitialQuery (packages/mongo/oplog_observe_driver.js:658:10)
2024-02-01T06:38:00.149996+00:00 app[web.1]:     at packages/mongo/oplog_observe_driver.js:191:10
2024-02-01T06:38:00.149996+00:00 app[web.1]:     at packages/mongo/oplog_observe_driver.js:15:9
2024-02-01T06:38:00.149997+00:00 app[web.1]:     at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1234:12)
2024-02-01T06:38:00.149997+00:00 app[web.1]:     at packages/meteor.js:550:25
2024-02-01T06:38:00.149997+00:00 app[web.1]:     at runWithEnvironment (packages/meteor.js:1286:24) {
2024-02-01T06:38:00.149997+00:00 app[web.1]:   name: 'MongoError',
2024-02-01T06:38:00.149997+00:00 app[web.1]:   [Symbol(mongoErrorContextSymbol)]: {}
2024-02-01T06:38:00.149998+00:00 app[web.1]: }

So it appears that oplogs may not be working on the new server. Since the server shares the exact same codebase, we thought it must be something related to the new database. But we couldn't be sure what was wrong as we were not the one who configured the oplog in the legacy original server.

Both the old and new servers has the following environment variables configured:

OLD SERVER
MONGO_OPLOG_URL
mongodb+srv://user:password@oldclusterxxx.gogvv.mongodb.net/local
MONGO_URL
mongodb+srv://user:password@oldclusterxxx.gogvv.mongodb.net/database_name
NEW SERVER
MONGO_OPLOG_URL
mongodb+srv://user:password@newclusteryyy.gogvv.mongodb.net/local
MONGO_URL
mongodb+srv://user:password@newclusteryyy.gogvv.mongodb.net/databse_name

Also checked the networking IP address restrictions, which has no restrict so we can rule out the possibilities that the new database has IP restrictions.

So what could be the problem in the new database that causes this MongoError: no primary server available in oplog operations?

OLD APP
MongoDB 4.4.28 
Meteor 1.10.2 
mongo@1.10.0

NEW APP
MongoDB 5.0.24 
Meteor 1.10.2 
mongo@1.10.0

​

Hi,

Please check this question posted on meteor forums

https://forums.meteor.com/t/url-is-not-available-to-google-error-in-google-search-console/60699

My error only happens on ipads (which is the main device of my client) you can sign in and go whereever you want but after you refresh the page it starts blinking like crazy not allowing you to press any buttons or scroll.

Anyone know what this issue could be? I am using Meteor 1.9.2

Errors on video:

https://reddit.com/link/160g8gd/video/4g6bu21pu4kb1/player

https://reddit.com/link/160g8gd/video/o4cxg91pu4kb1/player

​

Hello meteorites 👋

I'm one of the open-source contributors of Flowbite and these past few days I've been talking with the maintainers of Meteor.js to work together and build and integration guide for the UI components from Flowbite, Meteor.js and Tailwind CSS.

The guide was also posted on the official Meteor.js guide page and we hope that we can work together in the future to provide even more in-depth integration with this awesome framework.

Just though I would share it with the community on Reddit too and I'm very curious about your opinion and feedback of this new integration and UI component library for the Meteor.js ecosystem.

I am adding a new feature which will save the customers card data in stripe to facilited when they want to make new purchases in the plataform.

The idea is that when they want to make a payment again I will request the data to stripe, show last 4 numbers and only with writing the cvc it will make a new purchase.

I using this docs as guide but I always ecounter issues with the clientSecret.

https://stripe.com/docs/stripe-js/react

I've been bashing my head against the keyboard for 1 week now. I cannot make a coverage report for test in meteor packages no matter what i try.

Has anyone manged to do it? Is there any working example repo?

DDP was introduced in 2012

https://blog.meteor.com/introducing-ddp-6b40c6aff27d

His spec is presented in doc:

https://github.com/meteor/meteor/blob/devel/packages/ddp/DDP.md

​

And in my opinion is perfect to maintain sync of json collection between two machines connected by websocket.

​

But none of 3 npm libraries that allow to use DDP without Meteor not break 1k downloads per week

https://www.npmjs.com/package/ddp

https://www.npmjs.com/package/simpleddp

https://www.npmjs.com/package/node-ddp-client

​

I am considering DDP as solution for state synchronization by websocket in t3 stack without meteor, but afraid that I am missing some DDP drawbacks.

​

Can anyone explain me why adoption is so low? Or what are biggest problems with DDP?

Hi there, I am currently doing research for my blog about Meteor.js. Can you guys please help me know the nearby count with a source that how many meteor.js smart packages are available in its official repository?

Hey guys, I have been trying to schedule an email to be send in three after the customers makes a purchase and I am having trouble doing so. I havetried using node-cron library inside a method but did not get results.

I just get a "res undefined" in the navigator console and no error in my terminal.

Code:

I know is not schedule for three years yet, is schedule for 1 minute but the email is never sent even the "mail.sendMail" works perfect.

"shop.3years"() {
const cron = require("node-cron");
      cron.schedule("* * * * *", function () {         Meteor.call( "mail.sendMail", "Reminder", "test@gmail.com", "Reference: 321", "Hi in 3 years.", function (error, result) { if (error) {               console.log("error", error);             }else{               console.log("result", result);             }           }         );       });     },

​

I was hoping someone here with experience upgrading Meteor would come riding in and basically save the project, as we can't onboard new devs anymore. There are too many conflicts when setting up local host, the app isn't stable enough and everyone gives up and disappears. Upgrading to the latest Meteor version would fix that.

Here's the project: https://github.com/focallocal/fl-maps

Here's a post where i've pulled together all the PRs from our last attempt at upgrading Meteor (..perhaps Tom just missed something small): https://publichappinessmovement.com/t/topic/2832/9

If we can get this fixed our platform is just a few weeks away from helping people who are homeless all around the world, which i am painfully desperate to see after so many years building. Anyone who wants to help is very welcome to stick around and be part of the community long term too.

I am making a big Meteor React Js project and I am stuck in a part where I need to print many documents.

I have been using HTML2CANVAS but since only takes a picture and does not detect the content it cuts randomly into pages when the content is too long, making it look bad.

I tried using React-pdf but it throws an error because is an old version of Meteor that I can not update since will cause many conflicts around the project.

Does anybody know any other way in which I could print high-quality pdf from my divs without getting them cut randomly?