Fredrik Höglund

I agree with the conclusion that we simply don't support this right now, but I do think we should if we can (I've also run into these cases and have...

I don't have many opinions really, but I do have observations. Your explanation why this is happening is great and makes total sense, but if you only look at the...

FWIW I agree this specific bug is a bit niche and there's indeed a good userland workaround, hoist the `useQuery` to outside the Suspense boundary as you demonstrate, so I...

> The cache entry could definitely be observed by a different component, for example, the devools will show it. We could try to bend the rules here but I’m not...

> Yeah, you can just not use(promise) if the query is disabled. It wouldn’t solve this issue though, right? For sure, I'm definitely discussing several things here. API design/optimal behaviour...

> that’s certainly interesting - so you think writing to a context / outside store during render that is not observed by any react component would be fine? I'm not...

Re: `useSuspenseQuery` enabled > conditional return types could do this I think I experimented with this a bit and turns out that it sure can work with explicit `true` and...

For a bundled build, directives like `'use client'` is indeed all or nothing which is unfortunate. Is there anything stopping Rollup from preserving these directives when `preserveModules: true` though? If...

I did some digging into this to see if it was something I could contribute on. I found where this is happening: https://github.com/rollup/rollup/blob/master/src/ast/nodes/ExpressionStatement.ts Being unfamiliar with the code base and...

> Yes, imports are removed and completely rewritten in the finalizers. To preserve directives, one would need to pass the directive to the finalizer, which is a bigger refactoring of...