GraphiQL

The official reference @GraphQL IDE implementation, est. 2015 (header photo includes @OneGraph)

[GraphiQL @GraphiQL]

See more: https://t.co/beIfDJQXDX

Try it: npm i [email protected]

[GraphiQL @GraphiQL]

Try the first alpha of [email protected]!

• Replaces reach-ui with unstyled radix and headlessui
• Reorder tab! (thanks https://t.co/XNWsfuLxVD)

The next alpha will include a much awaited monaco editor that replaces codemirror

[GraphiQL @GraphiQL]

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

[Laurin Quast @n1rual]

We finally upgraded to
@GraphiQL v2 🥰 https://t.co/41qrCzcqLD

[GraphiQL @GraphiQL]

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

[GraphiQL @GraphiQL]

Has your favorite #GraphQL product and/or framework integrated graphiql@2 yet?

RT with a live example or screenshot!

[GraphiQL @GraphiQL]

@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 @GraphiQL]

Though [email protected] 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?!

[GraphiQL @GraphiQL]

Thanks to our co-maintainer @imolorhe from @AltairGraphQL , we are now shipping a modern @codemirror 6 mode called cm6-graphql! 🚀

https://t.co/h35qCdT5Qz

[GraphiQL @GraphiQL]

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

https://t.co/4CTpNF8gMK

[andi marek @andimarek]

People keep guessing how much #GraphQL is actually used, which I think is natural for every interesting technology. But hard numbers are extremely rare to find, so here is some background and never shared before statistics (1/n)

[GraphiQL @GraphiQL]

@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 @GraphiQL]

[email protected] 🚀
graphql language service [email protected]

✅ @vuejs (& @sveltejs) support! thanks @aumy_f for making that happen!!
✅ important bugfixes for no graphql-config contexts!

[GraphiQL @GraphiQL]

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

[GraphiQL @GraphiQL]

coming soon to the LSP server & vscode graphql:

☑️ workspaces support
☑️ major perf improvements!

[Gatsby @GatsbyJS]

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:

[GraphiQL @GraphiQL]

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

https://t.co/es26hI2V6a

[Jamie Barton 🥕 @notrab]

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

[GraphiQL @GraphiQL]

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)

[GraphiQL @GraphiQL]

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!

[GraphiQL @GraphiQL]

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!

https://t.co/6D2qanYiyC

[GraphiQL @GraphiQL]

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