Phil Pluckthun

yep! that's exactly what I meant 👍 You've got it spot on. Happy to take over implementation but also happy to accept a PR for this

I'm a bit ambivalent whether this goes into `@urql/core` or into a separate `exchanges/*` package first. The latter could help us test this in isolation first, and we can always...

I did have a quick look, and it sure doesn't seem trivial 👍 We've discovered this due to the `swr` package. They seem to be doing what I implemented a...

Please don't reply with bumps to issues. It's not great etiquette since it spams people with ping notifications and don't add more information to issues. Once an issue is accepted...

I might be misremembering this, but I think we actually used to have a `rootTypeNames` option (or something named similarly?) but got rid of it in favour of being able...

Superseded by #41613 to apply suggestions

I believe I've observed similar problems and noted them down. I haven't been able to investigate this much yet since I'm not super familiar with the relevant code, but a...

`expo` itself exposes the API surface here, so no sub-module path is needed: https://github.com/expo/expo/blob/c1586aba83225dfd8e683cadd05afc2b7c54c019/packages/expo/src/Expo.ts#L8-L32 If something's missing it should be added (there's not much, but some of our internal packages...

Current Progress: - #41264 is needed due to self-resolution not working without a `node_modules` structure with `require.resolve` in CommonJS - #41309 is needed to update Expo Go resolution (otherwise, `expo-av`...