GraphiQL

See more: npmjs.com/package/graphi… Try it: npm i graphiql@3.0.0-alpha.0

Try the first alpha of graphiql@3.0.0! • Replaces reach-ui with unstyled radix and headlessui • Reorder tab! (thanks github.com/mylesmmurphy) The next alpha will include a much awaited monaco editor that replaces codemirror

@nsfounder @n1rual we have supported the experimental defer/stream spec since ~ fall 2020! see @graphiql/toolkit

@n1rual @GraphiQL Very nice, do you have any plan on supporting the graphql 17 defer spec with the new executor ? github.com/graphql/graphq….

We just release GraphQL Yoga v3 🚀🎉🍾🎈 github.com/dotansimha/gra…

We finally upgraded to @GraphiQL v2 🥰 the-guild.dev/graphql/yoga-s…

roughly 30-40% of our weekly npm downloads are now in the 2.x.y range! The #graphql community is levelling up!

Has your favorite #GraphQL product and/or framework integrated graphiql@2 yet? RT with a live example or screenshot!

@kidehen a custom results component prop (essentially a plugin) would allow you to render results as this instead of JSON! hoping to advance this new prop as well as everything else, hopefully in a minor release before 3.0.0

@GraphiQL is there a variant of your cool interactive #GraphQL query interface that includes support for #HTTP #URLs as live hyperlinks in query results? Here's a jsoncrack.com variant of what I am asking about. tinyurl.com/5sar85sx #DataAccess #DataConnectivity

Though graphiql@3.0.0 will adopt monaco-graphql, we will not be abandoning the #codemirror community, as we feel that both monaco editor and codemirror 6 have immense value to our users in different contexts and use cases. A question remains - can/will graphiql@3 support both?!

Thanks to our co-maintainer @imolorhe from @AltairGraphQL , we are now shipping a modern @codemirror 6 mode called cm6-graphql! 🚀 npmjs.com/package/cm6-gr…

If anyone is wondering how popular #graphql is, I released a syntax highlighting extension in july (and just on vscode marketplace), now we're almost at 500K installs marketplace.visualstudio.com/items?itemName…

@aumy_f @vuejs @sveltejs Indeed! I added some tests out of curiosity and it seemed to work fine... I'm pretty sure the sfc compiler will just ignore attributes like <script context="module" which is fine for these simple purposes.

@GraphiQL @vuejs @sveltejs Oh I missed that Svelte support has been added 🙇‍♂️

vscode-graphql@0.8.1 🚀 graphql language service server@2.9.1 ✅ @vuejs (& @sveltejs) support! thanks @aumy_f for making that happen!! ✅ important bugfixes for no graphql-config contexts!

@aumy_f @vuejs @sveltejs I added the svelte support based off your vue support PR. Appears to be working to me! - Rikki (acao)

@GraphiQL @vuejs @sveltejs Hi, I have not added Svelte support and would like you to resubmit

coming soon to the LSP server & vscode graphql: ☑️ workspaces support ☑️ major perf improvements!

Did you know… A) the latest version of @GraphiQL is more accessible and has dark mode/tabs? B) you can get it in Gatsby 5 beta today? Check out this (no-sound) video for more:

What if: - fetcher was optional - environments prop allowed you to statically define configuration for multiple schemas - a network tab plugin allowed users to override this state - if you use environments prop, createGraphiQLFetcher() becomes internal github.com/graphql/graphi…

We also recently witnessed a brand new @GraphiQL release that boasts a powerful plugin ecosystem, fewer dependencies, and even dark mode!

TFW you see someone using your code on the train in the cafe car but you don't want to weird them out by revealing you looked at their screen 😂 I will be in AMS tonight and for the next week, what's good? - (Rikki aka acao on github)

This markdown example may seem far fetched, but you would be surprised! I've fielded at least one inquiry for this iirc (rikki). Requests to handle Yaml, JSON5, & binary formats like protobufs or msgpack are more common. @graphql userland is constantly pushing the envelope!

We start with a relatively simple example of JSON5. Configuring plugins by response content types, we could make handling additional, novel and ad-hoc content types possible, beyond the current spec

What if we had content-type aware response handler plugins like these? The limits of demonstrating future and/or novel #graphql specs would be boundless! github.com/graphql/graphi…