Eric Burel

Relevant thread on making the libraries tree-shakeable when they are rebuilt in the end user app (Next) and not just tree-shaked during the publication of the NPM package: https://github.com/egoist/tsup/issues/578

I suspect this is an issue in the default fragment generator @Timi-Duban , from package @vulcanjs/graphql

Another small issue: when document is not found, the hook will still try to update the lists using multiQueryUpdater => it should not

The most common issue I have is when I edit package A, and I notice I need a change in package B => I need to rebuild package B for...

This needs a change in Vulcan Meteor too, because the structure of the response is defined there.

Didn't know about that, thank you! The API would be more: ```ts interface FooData { foo : { data: { id : String } } } ``` because the data...

The style argument is indeed a good idea, as well has Heroku deploy. However I've never managed to do a git based deploy with a 2 repo install so if...

You probably need to add "vulcan-*" to your regex otherwise you may also match other packages instead of just Vulcan, however that's a good idea indeed

Many of those issues are Meteor wide btw, you could talk about it on the Meteor forums also. We have way less problems with NPM based solutions for instance, especially...

That could end up being confusing with the Next Starter and the Meteor Starter, we already use the name starter for this. Maybe "ui" is more generic?