io comments

Results 23 comments of

io

Call for maintainers

did ya have any luck?

Fix handling of empty JSON object response and no field selection

I'm not sure I follow @fbartho, this doesn't concern GraphQL parsing at all but rather an occasional scenario where some JSON APIs will respond with an empty object in some...

Fix handling of empty JSON object response and no field selection

Still not following. Every field of `Query`(or indeed `Mutation`) doesn't necessarily have fields.

AsyncIterator: Attempting to change value of a readonly property

Still seeing this around on 3.110.1

Add support for nullable primitives

Bump 😭

Next 13 fetch in server component stuck forever if response is larger than ~15kb

Sounds like a reprisal of this type of issue: - https://github.com/vercel/next.js/issues/39262 - https://github.com/vercel/next.js/pull/41270

Introduce UMD as a new output format

lesss goooo

Next js 13 moves all meta tags to the head tag including schema markup meta tags

We're experiencing this issue on 13.1.5 with `pages/` (not `app/`)

Next js 13 moves all meta tags to the head tag including schema markup meta tags

Another clue for this happening with `/pages` too (still in `13.1.6`) is that we are using suspense in that universe (via `@tanstack/query`)

Next js 13 moves all meta tags to the head tag including schema markup meta tags

Turns out my problem, which I think is in fact separate from this one, was caused in my project by using `react@next` (`18.3.0-next-0f4a83596-20230110` to be precise). Returning to `[email protected]` has...