Eric Burel

CollectionPropsWrapper do not really generate a fragment but get the collection based on either a "collection" props or the "collectionName". So I guess the faulty fragment is just the default...

Maybe here: `packages/getting-started/lib/modules/schema.js`, in the `userId` schema I am not sure whether we preserve the `userId` field when adding the `user` resolver => that may break permissions?

Blackbox objects might be rendered as a stringified JSON instead

No problem! Vulcan Meteor development is not active, we are currently focused on the Next.js version

Hi, it could be an occurrence of the bug where Meteor exports an empty object instead of the actual export server side: https://github.com/VulcanJS/Vulcan/issues/2580 Does the page still load client side?...

I think we could split them into a separate package maybe, but still in Vulcan core repo Because you might want to use them in other apps in the future

@webface If you are creating a new application, you might prefer using Vulcan Next instead of the "legacy" Vulcan Meteor project which is less active, and in particular often generating...

Most of them for the backend at this point, basically you can reuse Vulcan schemas to spawn a graphql API + mongo collection, and you have React hooks as well...

Still happens after updating to meteor v2

Sounds pretty good ! I am not a huge mobile user and I don't know much about PWAs, I'll link your pr on the Slack