Gerald Monaco

Very sorry for the delay, I've been swamped with other things. Will review this today or tomorrow!

We've moved the polyfill to maintenance mode and aren't currently considering additional features. For Web Component + Shadow DOM support, I'd encourage you to continue to follow @Marshal27 who was...

Thank you for your patience, everyone. Now that #55130 has landed, you can enable the developer preview for i18n hydration support in the latest pre-release (v18.0.0-next.4) by using: ```tsx import...

@jelbourn @alxhub

@Marshal27 Thank you for all of your hard work on this PR. This is an important feature that many folks are passionate about, and one that I had hoped we'd...

@rmosolgo's approach is how I am securing particular queries/mutations/fields. In our case, we don't care that we might expose some authorized user only fields or mutations via introspection. Even if...

Hi Mike. Could you provide a little more information about your scenario? When is ‘aaa.object’ being changed? Why is it changing? If it’s through a mutation, why isn’t the mutation...

I think you can get the same effect as your click hack by using: ``` flushSync(() => { root.unstable_scheduleHydration(document.getElementById("body")); }); ``` This doesn't help you in Next.js, since it doesn't...

Right -- I think the underlying concern is just that known-but-invalid values are given special treatment (compared to `unknown` values). This means that it's more likely that some use case...

For what it's worth, when I opened the issue I was considering that `invalid()` would probably be something that _is_ valid in other (e.g. newer) browsers (as @mirisuzanne pointed out),...