Luis Alvarez D.

Hello! I'm no longer supporting this package because of lack of time and of the current state of Meteor, but I'm going to try to answer the question, I don't...

it was a performance and scalability decision, my current stack is Next.js + Apollo / Node. The solution you're using may work, if you can do it from the client...

Maybe at some point the internal implementation of minimongo changed and [this line](https://github.com/lfades/cottz-publish-relations/blob/master/lib/server/handler_controller.js#L20) may have broke.

Yeah, sorry about that. I'm not working with Meteor anymore, and even If I come back because I still think Meteor is great, I'll use Apollo Graphql instead of publish/subscribe.

when I write this package I saw publish-composite first and I didn't like it, because it's using the observers in a bad way. Most of the times you only need...

`publish-relations` also allow you to have non reactive cursors and joins, very useful when you're sure you don't need reactive data in some places :D (and very performant friendly)

I fixed the typo, thanks. I have a note under the example that points to the recommendations, there is the same example but with a join. When I have free...

try this: ``` js this.cursor(Meteor.users.find(this.userId, { limit: 1 }), function(id, doc) { if (doc.filters) { this.cursor(Products.find(doc.filters)); } }); ``` the problem can be when a different field is updated in...

check the update you are doing on the user, I'm not quite sure how to help there :S

**Update**: We (the Solutions Team at Vercel) were very busy working on the Next.js Conf and haven't had the time to put more work into Commerce, and we're currently looking...