Michiel ter Reehorst

The action could be simply be a "hard refresh" and restart the subscription, independent of the underlying protocol or library. Just like `useSubscription` is implementation independent. Something like this: ```typescript...

I think what I would like to achieve is what the [`shouldResubscribe` option](https://www.apollographql.com/docs/react/data/subscriptions/#options) does, but manually. To quote the docs: > Determines if your subscription should be unsubscribed and subscribed...

With the introduction of `@defer` and `@stream` the execute function actually can return an async iterator. This might be a great time to also allow subscription execution via the execute...

@dlehmhus, have you got any feedback or workaround for this issue? Running into the same problem. Updating to Next 13.2.4 doesn't seem to have this issue, but results in: ```...

@dlehmhus, thanks for your reply. In the meantime I've got our setup working with the latest versions of vercel, nx and nextjs: | Dependency | Version | |--------|--------| | vercel...

@trappar Nx version?

@trappar, I forgot this was a generic vercel issue, not just NX. For me it's working with node 18. What version of node are you on?

@glitch452, thanks for sharing! It's working for me as well in an NX monorepo library containing the translation files: ```javascript // libs/i18n/messages/eslint.config.js const { resolve } = require('node:path'); const i18nJsonPlugin...

@damienwebdev, did you ever had the opportunity to implement your proposal? It seems like a nice approach to just overrule the packages definition. FYI, we're using the same approach of...

@chris-pardy, thanks for looking into this! There is a use case where generic rules are in code and user/organisation specific rules are in the database. The code ones should, in...