Eric Burel

Relevant tutoriel: https://dev.to/jankapunkt/transform-any-meteor-app-into-a-pwa-4k44 @EloyID has managed to install it in a Vulcan app, it seems to work out of the box

@harryadel Yep nobody is working on this, more than happy to accept a PR

In which folder are you running Vulcan? The logic that create `schema.graphql` may not choose the right path on windows. It should be the root of your code. You indeed...

Logic is happening here: `packages/vulcan-lib/lib/server/debug.js` In the `logToFile` function, the path where `schema.graphql` is not constructed in a cross platform way, we should use `path.join` instead. I would happily accept...

This file is in the core Vulcan repo, you need a 2-repo install to tweak Vulcan itself: https://docs.vulcanjs.org/#Two-Repo-Install-Optional

I don't think we will make this an option, because in some distant future we might need a reliable prebuild step. It should probably live in the ".vulcan" folder though

We could reuse the `forEachDocumentField`, I've used it to implement permission check and dates conversion. It's not perfect but at least it can either be reused directly or at least...

Example schema that worked previously: https://github.com/GraemeFulton/letter-modules/tree/1.13.0/letters/sub-schemas https://github.com/GraemeFulton/letter-modules/blob/1.13.0/letters/schema.js

Also for array, when we add an item, we can be in an `update` mutation, while new items might want to run their `onCreate` function.

Another possibility is just renaming "guests" to be less prone to confusion, eg `anyone`. Because we often use the terme "guest" to describe specifically non-connected users, while in Vulcan it's...